From: Evgeniy Dushistov <dushistov@mail.ru>
To: Roel Kluin <12o3l@tiscali.nl>
Cc: lkml <linux-kernel@vger.kernel.org>,
Mark Fortescue <mark@mtfhpc.demon.co.uk>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] fs/ufs/util.h 2nd parameter of fs32_to_cpu is not boolean
Date: Sat, 16 Feb 2008 23:16:53 +0300 [thread overview]
Message-ID: <20080216201650.GA18444@rain> (raw)
In-Reply-To: <47B73BA7.1000004@tiscali.nl>
On Sat, Feb 16, 2008 at 08:38:15PM +0100, Roel Kluin wrote:
> from: fs/befs/endian.h +33
> static inline u32
> fs32_to_cpu(const struct super_block *sb, fs32 n)
> {
> if (BEFS_SB(sb)->byte_order == BEFS_BYTESEX_LE)
> return le32_to_cpu((__force __le32)n);
> else
> return be32_to_cpu((__force __be32)n);
> }
>
> The 2nd parameter is not boolean
> ---
> Test the return value, rather than passing a boolean
>
> Signed-off-by: Roel Kluin <12o3l@tiscali.nl>
> ---
> diff --git a/fs/ufs/util.h b/fs/ufs/util.h
> index b26fc4d..23ceed8 100644
> --- a/fs/ufs/util.h
> +++ b/fs/ufs/util.h
> @@ -58,7 +58,7 @@ ufs_set_fs_state(struct super_block *sb, struct ufs_super_block_first *usb1,
> {
> switch (UFS_SB(sb)->s_flags & UFS_ST_MASK) {
> case UFS_ST_SUNOS:
> - if (fs32_to_cpu(sb, usb3->fs_postblformat == UFS_42POSTBLFMT)) {
> + if (fs32_to_cpu(sb, usb3->fs_postblformat) == UFS_42POSTBLFMT) {
> usb1->fs_u0.fs_sun.fs_state = cpu_to_fs32(sb, value);
> break;
> }
Yeah, in origin patch, which introduced this code was the similar
misprint. It is sad that after review only one was fixed,
and the second go to mainline.
Acked-by: Evgeniy Dushistov <dushistov@mail.ru>
--
/Evgeniy
prev parent reply other threads:[~2008-02-16 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 19:38 [PATCH] fs/ufs/util.h 2nd parameter of fs32_to_cpu is not boolean Roel Kluin
2008-02-16 20:16 ` Evgeniy Dushistov [this message]
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=20080216201650.GA18444@rain \
--to=dushistov@mail.ru \
--cc=12o3l@tiscali.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mtfhpc.demon.co.uk \
/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.