[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080229192123.GB19476@elte.hu>
Date: Fri, 29 Feb 2008 20:21:23 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Matthew Wilcox <matthew@....cx>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-kernel@...r.kernel.org,
Matthew Wilcox <willy@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
linux-arch@...r.kernel.org
Subject: Re: [PATCH 11/12] Generic semaphore implementation
* Andrew Morton <akpm@...ux-foundation.org> wrote:
> yummy summary:
>
> 254 files changed, 386 insertions(+), 7827 deletions(-)
>
> The only major conflict is with avr32 which seems to have just done a
> major revamp of that architecture's semaphore implementation. Oh
> well.
>
> There are a couple of small #include rejects here and there, nothing
> at all major.
>
> Yes, let's get this into linux-next if poss please. If mainline later
> breaks for some architecture, well, we did our best..
a better approach would be to send the core bits to Linus right now - as
long as it's Kconfig isolated and inactive code - hence it is eligible
as a cleanup.
That means arch maintainers could start applying the patches at their
own pace, starting right now, in their own work-flow and test-flow.
(obviously, the first such patches would hit mainline starting in the
next merge window)
And all the linux-next integration trouble down the line is avoided, and
each architecture can do a concentrated effort of: 'get rid of semaphore
code'.
Please!
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists