Re: ACPI & 2.4 (Re: [BK PATCH] PCI Express patches for 2.4.27-pre3)

[Marcelo Tosatti]

On Fri, May 28, 2004 at 10:56:50AM -0400, Len Brown wrote:
> On Fri, 2004-05-28 at 08:09, Marcelo Tosatti wrote:
> > On Wed, May 26, 2004 at 03:35:34AM -0400, Len Brown wrote:
> 
> > > I generally only have time to read LKML messages directed to me
> > > or if the word "ACPI" appears in the message, so I may have missed
> > > the word 2.4.  What is the word?
> > 
> > I dont get you? What you mean? (sorry)
> 
> If you announced a change in policy for accepting 2.4 patches,
> then I missed it.  So I'm assuming that since people are still
> complaining to me about bugs in 2.4, and we're all still fixing
> those bugs, that I should continue to submit those patches to you.

Perfect. 

> I understand that we should not add any new features to 2.4,
> and that we should not undertake any significant code cleanups
> because the tolerance for risk is low.

Right.

> For these reasons, the ACPI code in 2.6 is starting to diverge
> from 2.4.  However, large parts of the ACPI sub-system, such
> as the core intepreter and most of the configuration code,
> are very much the same betwen 2.4 and 2.6.  For this reason
> I think the risk is low to integrate some relatively large
> ACPI patches into 2.4 -- as long as the same code has already
> been tested and released in 2.6.

Hum, fine. That sounds more conservative.

> So I can delay sending 2.4 patches until it is clear that they
> were successful in 2.6.  The question I have is how long there
> will be a 2.4 release available for accepting those patches.

The policy now is to accept only bugfixes and support for new
hardware (eg new PCI ID's, new drivers). There will still be
a few v2.4 releases, just not with the same frequency as they have
been released in the past.

Does that answer your question?


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/