[fedora-arm] 4.0 final, 4.1 merge window, and us

[Al Stone]

On 04/14/2015 06:53 AM, Josh Boyer wrote:
> On Tue, Apr 14, 2015 at 8:05 AM, Peter Robinson <pbrobinson at gmail.com> wrote:
>> On Tue, Apr 14, 2015 at 12:51 PM, Josh Boyer <jwboyer at fedoraproject.org> wrote:
>>> Hi All,
>>>
>>> The 4.0 final release is in rawhide and submitted for an update for
>>> Fedora 22 now.  Given the release schedules for 4.1 and F22, we're
>>> going to stick with 4.0 for F22 GA.  Please stick to fixes for F22 and
>>> we'll no longer keep that branch in sync with rawhide.
>>>
>>> The 4.1 merge window is open and active upstream as well.  I'll be
>>> rebasing rawhide to those kernels likely later today or tomorrow.  If
>>> you have things that are landing in 4.1 that you'd like enabled,
>>> please let us know.  The only major feature I'm aware of that might
>>> land is kdbus, but the jury is still out on that one.
>>
>> The ACPI 5.1 patch set I believe is on it's way in for this cycle so
>> we'd like that for aarch64 in F-23 (possibly not in F-22 but 4.1 for
>> that is a while out) but I'm unsure of the impact there on x86 too,
>> I'd assume nothing, but happy to coordinate with you as appropriate
>> there.
> 
> Good to know.  As far as I'm aware, new ACPI code drops just go into
> the tree and are picked up automatically on all architectures that use
> them and have it enabled.  I'll keep an eye out for this on aarch64
> but I don't expect any impacts on x86 beyond the normal code drop kind
> of issues.

As co-author of those patches, the last I heard we were in linux-next,
and could possibly be merged into 4.1; there may be some push back that
would cause it to be delayed to 4.2, but that's uncertain.

The patches themselves should have no effect on any other architecture
that uses ACPI; they haven't yet, but I'm just paranoid enough to think
it's not impossible :).

-- 
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3 at redhat.com
-----------------------------------