From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Matthew Wilcox <matthew@wil.cx>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 11/12] Generic semaphore implementation
Date: Fri, 29 Feb 2008 20:21:23 +0100 [thread overview]
Message-ID: <20080229192123.GB19476@elte.hu> (raw)
In-Reply-To: <20080228174349.1da254bd.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-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
next prev parent reply other threads:[~2008-02-29 19:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 0:36 [PATCHES] semaphore rewrite Matthew Wilcox
2008-02-28 6:33 ` [PATCH 01/12] Fix quota.h includes Matthew Wilcox
2008-02-28 6:33 ` [PATCH 02/12] Add semaphore.h to kernel_lock.c Matthew Wilcox
2008-02-28 6:33 ` [PATCH 03/12] arch: Remove unnecessary inclusions of asm/semaphore.h Matthew Wilcox
2008-02-28 6:33 ` [PATCH 04/12] net: " Matthew Wilcox
2008-02-28 6:33 ` [PATCH 05/12] drivers: " Matthew Wilcox
2008-02-28 6:33 ` [PATCH 06/12] fs: " Matthew Wilcox
2008-02-28 6:33 ` [PATCH 07/12] include: " Matthew Wilcox
2008-02-28 6:33 ` [PATCH 08/12] kernel: " Matthew Wilcox
2008-02-28 6:33 ` [PATCH 09/12] lib: " Matthew Wilcox
2008-02-28 6:33 ` [PATCH 10/12] security: " Matthew Wilcox
2008-02-28 6:34 ` [PATCH 11/12] Generic semaphore implementation Matthew Wilcox
2008-02-28 6:34 ` [PATCH 12/12] Convert asm/semaphore.h users to linux/semaphore.h Matthew Wilcox
2008-02-28 7:18 ` [PATCH 11/12] Generic semaphore implementation Ingo Molnar
2008-02-29 0:39 ` Matthew Wilcox
2008-02-29 0:50 ` Harvey Harrison
2008-02-29 1:43 ` Andrew Morton
2008-02-29 5:30 ` Matthew Wilcox
2008-02-29 17:42 ` Haavard Skinnemoen
2008-02-29 19:21 ` Ingo Molnar [this message]
2008-02-29 2:00 ` Stephen Rothwell
2008-02-29 2:10 ` Andrew Morton
2008-02-29 5:32 ` Matthew Wilcox
2008-02-29 6:43 ` Stephen Rothwell
2008-02-29 16:14 ` Linus Torvalds
2008-02-29 1:57 ` Andrew Morton
2008-02-29 5:43 ` Matthew Wilcox
2008-02-29 2:37 ` Harvey Harrison
2008-02-29 2:47 ` [PATCH] semaphore: remove likely/unlikely annotations Harvey Harrison
2008-03-03 14:54 ` [PATCH 11/12] Generic semaphore implementation Matthew Wilcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080229192123.GB19476@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=willy@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox