From: "Hannes Eder" <hannes@hanneseder.net>
To: "Jan Kara" <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
trivial@kernel.org
Subject: Re: [PATCH] udf: fix sparse warnings
Date: Mon, 1 Dec 2008 15:55:58 +0100 [thread overview]
Message-ID: <154e089b0812010655l10a90c38m5a0cf3e93a910b36@mail.gmail.com> (raw)
In-Reply-To: <20081201120951.GD17303@duck.suse.cz>
On Mon, Dec 1, 2008 at 1:09 PM, Jan Kara <jack@suse.cz> wrote:
> On Thu 27-11-08 23:12:55, Hannes Eder wrote:
>> Fix this sparse warnings:
>>
>> fs/udf/balloc.c:843:3: warning: returning void-valued expression
>> fs/udf/balloc.c:847:3: warning: returning void-valued expression
>> fs/udf/balloc.c:851:3: warning: returning void-valued expression
>> fs/udf/balloc.c:855:3: warning: returning void-valued expression
>>
>> Signed-off-by: Hannes Eder <hannes@hanneseder.net>
> Thanks for the patch. But when we are at it, I'd rather go for the
> following change:
>
> From f3facf9a4a60bba9f1fa0c779fc441c6aff90eb4 Mon Sep 17 00:00:00 2001
> From: Jan Kara <jack@suse.cz>
> Date: Mon, 1 Dec 2008 13:06:10 +0100
> Subject: [PATCH] udf: fix sparse warnings:
>
> Fix sparse warnings:
>
> fs/udf/balloc.c:843:3: warning: returning void-valued expression
> fs/udf/balloc.c:847:3: warning: returning void-valued expression
> fs/udf/balloc.c:851:3: warning: returning void-valued expression
> fs/udf/balloc.c:855:3: warning: returning void-valued expression
>
> Reported-by: Hannes Eder <hannes@hanneseder.net>
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> fs/udf/balloc.c | 23 +++++++++--------------
> 1 files changed, 9 insertions(+), 14 deletions(-)
>
> diff --git a/fs/udf/balloc.c b/fs/udf/balloc.c
> index c0e87db..cde1a0d 100644
> --- a/fs/udf/balloc.c
> +++ b/fs/udf/balloc.c
> @@ -840,24 +840,19 @@ void udf_free_blocks(struct super_block *sb, struct inode *inode,
> struct udf_part_map *map = &UDF_SB(sb)->s_partmaps[partition];
>
> if (map->s_partition_flags & UDF_PART_FLAG_UNALLOC_BITMAP) {
> - return udf_bitmap_free_blocks(sb, inode,
> - map->s_uspace.s_bitmap,
> - bloc, offset, count);
> + udf_bitmap_free_blocks(sb, inode, map->s_uspace.s_bitmap,
> + bloc, offset, count);
> } else if (map->s_partition_flags & UDF_PART_FLAG_UNALLOC_TABLE) {
> - return udf_table_free_blocks(sb, inode,
> - map->s_uspace.s_table,
> - bloc, offset, count);
> + udf_table_free_blocks(sb, inode, map->s_uspace.s_table,
> + bloc, offset, count);
> } else if (map->s_partition_flags & UDF_PART_FLAG_FREED_BITMAP) {
> - return udf_bitmap_free_blocks(sb, inode,
> - map->s_fspace.s_bitmap,
> - bloc, offset, count);
> + udf_bitmap_free_blocks(sb, inode, map->s_fspace.s_bitmap,
> + bloc, offset, count);
> } else if (map->s_partition_flags & UDF_PART_FLAG_FREED_TABLE) {
> - return udf_table_free_blocks(sb, inode,
> - map->s_fspace.s_table,
> - bloc, offset, count);
> - } else {
> - return;
> + udf_table_free_blocks(sb, inode, map->s_fspace.s_table,
> + bloc, offset, count);
> }
> + return;
> }
>
> inline int udf_prealloc_blocks(struct super_block *sb,
> --
> 1.6.0.4
I prefer your version. I though about it as well, but then tried to
do kind of 'minimal change' patch, and leave the control flow as is.
Hannes
next prev parent reply other threads:[~2008-12-01 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 22:12 Hannes Eder
2008-12-01 12:09 ` Jan Kara
2008-12-01 14:55 ` Hannes Eder [this message]
2008-12-01 21:04 ` Bob Copeland
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=154e089b0812010655l10a90c38m5a0cf3e93a910b36@mail.gmail.com \
--to=hannes@hanneseder.net \
--cc=jack@suse.cz \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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
all inboxes | Powered by JetHome®