From: Ted Ts'o <tytso@mit.edu>
To: akpm@linux-foundation.org
Cc: linux-ext4@vger.kernel.org, akinobu.mita@gmail.com,
adilger.kernel@dilger.ca
Subject: Re: [patch 1/1] ext4: use proper little-endian bitops
Date: Wed, 28 Dec 2011 20:34:31 -0500 [thread overview]
Message-ID: <20111229013431.GJ12370@thunk.org> (raw)
In-Reply-To: <201111152256.pAFMu6Xw017147@wpaz9.hot.corp.google.com>
On Tue, Nov 15, 2011 at 02:56:06PM -0800, akpm@linux-foundation.org wrote:
> From: Akinobu Mita <akinobu.mita@gmail.com>
> Subject: ext4: use proper little-endian bitops
>
> ext4_{set,clear}_bit() is defined as __test_and_{set,clear}_bit_le() for
> ext4. Only two ext4_{set,clear}_bit() calls check the return value. The
> rest of calls ignore the return value and they can be replaced with
> __{set,clear}_bit_le().
>
> This changes ext4_{set,clear}_bit() from __test_and_{set,clear}_bit_le()
> to __{set,clear}_bit_le() and introduces ext4_test_and_{set,clear}_bit()
> for the two places where old bit needs to be returned.
>
> This ext4_{set,clear}_bit() change is considered safe, because if someone
> uses these macros without noticing the change, new ext4_{set,clear}_bit
> don't have return value and causes compiler errors where the return value
> is used.
>
> This also removes unused ext4_find_first_zero_bit().
>
> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
> Cc: "Theodore Ts'o" <tytso@mit.edu>
> Cc: Andreas Dilger <adilger.kernel@dilger.ca>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Applied.
- Ted
next prev parent reply other threads:[~2011-12-29 1:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 22:56 [patch 1/1] ext4: use proper little-endian bitops akpm
2011-12-29 1:34 ` Ted Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-28 20:55 akpm
2011-07-29 9:43 ` Lukas Czerner
2011-07-29 10:55 ` Akinobu Mita
2011-07-29 11:51 ` Lukas Czerner
2011-07-29 12:13 ` Amir Goldstein
2011-07-29 12:25 ` Akinobu Mita
2011-07-29 12:41 ` Lukas Czerner
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=20111229013431.GJ12370@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@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 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.