From: Jiri Slaby <jirislaby@gmail.com>
To: caglar@pardus.org.tr
Cc: linux-kernel@vger.kernel.org, dedekind@linutronix.de,
haver@vnet.ibm.com, torvalds@linux-foundation.org
Subject: Re: [PATCH] Silent compiler warning introduced by commit 801c135ce73d5df1caf3eca35b66a10824ae0707 (UBI: Unsorted Block Images)
Date: Sun, 10 Feb 2008 09:39:05 +0100 [thread overview]
Message-ID: <47AEB829.8060104@gmail.com> (raw)
In-Reply-To: <200802100537.47634.caglar@pardus.org.tr>
On 02/10/2008 04:37 AM, S.Çağlar Onur wrote:
> Hi;
>
> Following patch silents
>
> drivers/mtd/ubi/vmt.c: In function `ubi_create_volume':
> drivers/mtd/ubi/vmt.c:379: warning: statement with no effect
>
> compiler warning introduced by commit 801c135ce73d5df1caf3eca35b66a10824ae0707 (UBI: Unsorted Block Images)
>
> Signed-off-by: S.Çağlar Onur <caglar@pardus.org.tr>
>
> drivers/mtd/ubi/vmt.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mtd/ubi/vmt.c b/drivers/mtd/ubi/vmt.c
> index a3ca225..eafeaf0 100644
> --- a/drivers/mtd/ubi/vmt.c
> +++ b/drivers/mtd/ubi/vmt.c
> @@ -376,7 +376,7 @@ out_sysfs:
> get_device(&vol->dev);
> volume_sysfs_close(vol);
> out_gluebi:
> - ubi_destroy_gluebi(vol);
> + err = ubi_destroy_gluebi(vol);
> out_cdev:
> cdev_del(&vol->cdev);
> out_mapping:
I think this is not correct. You change the err which caused the failure. You
change it even to 0 if it doesn't fail and the whole function will seem like
non-failing.
next prev parent reply other threads:[~2008-02-10 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 3:37 [PATCH] Silent compiler warning introduced by commit 801c135ce73d5df1caf3eca35b66a10824ae0707 (UBI: Unsorted Block Images) S.Çağlar Onur
2008-02-10 8:39 ` Jiri Slaby [this message]
2008-02-10 23:44 ` S.Çağlar Onur
2008-02-12 9:33 ` Artem Bityutskiy
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=47AEB829.8060104@gmail.com \
--to=jirislaby@gmail.com \
--cc=caglar@pardus.org.tr \
--cc=dedekind@linutronix.de \
--cc=haver@vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox