linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nick Piggin <npiggin@suse.de>, Linux Arch <linux-arch@vger.kernel.org>
Subject: [patch 0/8] lock bitops and some bitops fixes
Date: Tue, 28 Aug 2007 18:14:53 +1000	[thread overview]
Message-ID: <20070828081453.13582.258.sendpatchset@linux.local0.net> (raw)

[Sent again with the correct date stamps, sorry for the noise :(]

Here is a new set of bitops patches that can hopefully get into the
next merge window.

I'm not sending the intrusive part of the patchset (the page lock and
buffer lock conversions), so that you'll hopefully apply these bits
and get them some early testing. I've just converted bit_spinlock
over to use the lock bitops, in order to get a bit of test coverage.

I've spotted some potential bugs in alpha and mips bitops functions,
but would like acks from maintainers for _those_ specific patches.

Thanks,
Nick

             reply	other threads:[~2007-08-28  8:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-28  8:14 Nick Piggin [this message]
2007-08-28  8:15 ` [patch 1/8] bitops: introduce lock ops Nick Piggin
2007-08-28  8:15 ` [patch 2/8] alpha: fix bitops Nick Piggin
2007-08-28  8:15 ` [patch 3/8] alpha: lock bitops Nick Piggin
2007-08-28  8:15 ` [patch 4/8] ia64: " Nick Piggin
2007-08-28  8:15 ` [patch 5/8] mips: fix bitops Nick Piggin
2007-08-28  8:15 ` [patch 6/8] mips: lock bitops Nick Piggin
2007-08-28  8:16 ` [patch 7/8] powerpc: " Nick Piggin
2007-08-28  8:16 ` [patch 8/8] bit_spin_lock: use " Nick Piggin
  -- strict thread matches above, loose matches on Subject: below --
2007-08-04 20:28 [patch 0/8] lock bitops and some bitops fixes 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=20070828081453.13582.258.sendpatchset@linux.local0.net \
    --to=npiggin@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-arch@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).