From: Andrew Morton <akpm@linux-foundation.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-arch@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [patch 1/7] bitops: introduce lock bitops
Date: Thu, 26 Jul 2007 01:05:22 -0700 [thread overview]
Message-ID: <20070726010522.0faeab97.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070725113407.GG29011@wotan.suse.de>
On Wed, 25 Jul 2007 13:34:07 +0200 Nick Piggin <npiggin@suse.de> wrote:
> I'd like to get the new lock bitop primitives in if possible. Maybe it
> is too late for 2.6.23, but at least if I can queue them up in -mm?
>
> They are pretty simple, but at least the page lock and buffer lock
> conversions touch quite a lot of code.
The changes look innocuous enough. I'd prefer not to carry this for two
months though.
afacit all the operations which got changed were actually renamed, so any
unconverted code will reliably fail to compile, yes? (If not, can we find
a way to do this?). This means that a) if I _were_ to carry if for two
months, any new code which gets added using the old operations will get
reliably detected and b) there's not really much benefit in me carrying it
all for two months.
> Not sure how to really do this
> better to reduce merge difficulties.
Resend around the -rc5/6 timeframe?
next prev parent reply other threads:[~2007-07-26 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 11:34 [patch 1/7] bitops: introduce lock bitops Nick Piggin
2007-07-25 11:34 ` [patch 2/7] tasklet_lock use " Nick Piggin
2007-07-25 11:37 ` [patch 3/7] wait_bit: " Nick Piggin
2007-07-25 11:38 ` [patch 4/7] bit_spinlock: " Nick Piggin
2007-07-25 11:39 ` [patch 5/7] page lock: " Nick Piggin
2007-07-25 11:40 ` [patch 6/7] buffer " Nick Piggin
2007-07-25 11:41 ` [patch 7/7] powerpc: optimised " Nick Piggin
2007-07-25 21:31 ` Benjamin Herrenschmidt
2007-07-25 11:44 ` [patch][rfc] ia64: " Nick Piggin
2007-07-25 14:40 ` [patch 1/7] bitops: introduce " David Howells
2007-07-26 0:44 ` Nick Piggin
2007-07-26 8:05 ` Andrew Morton [this message]
2007-07-26 8:15 ` Nick Piggin
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=20070726010522.0faeab97.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-arch@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.