All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Yongqiang Yang <xiaoqiangnk@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4:quiet 'unsed variables' compiling warnings.
Date: Mon, 27 Jun 2011 16:34:42 -0400	[thread overview]
Message-ID: <20110627203442.GF2729@thunk.org> (raw)
In-Reply-To: <1308108420-13799-1-git-send-email-xiaoqiangnk@gmail.com>

On Wed, Jun 15, 2011 at 11:27:00AM +0800, Yongqiang Yang wrote:
> Delete unused variables.
> 
> Signed-off-by: Yongqiang Yang <xiaoqiangnk@gmail.com>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index 859f2ae..fece8c2 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -2860,7 +2860,7 @@ ext4_mb_normalize_request(struct ext4_allocation_context *ac,
>  {
>  	int bsbits, max;
>  	ext4_lblk_t end;
> -	loff_t size, orig_size, start_off;
> +	loff_t size, start_off;

Unfortunately, orig_size is being used by an mb_debug statement.  So
simply removing orig_size and its initialization will cause the build
to break if CONFIG_EXT4_DEBUG is enabled.

Can you resend this patch with this part of the patch removed?

Also, for future reference I prefer for consistency's sake that the
one-line summary be:

ext4: quiet 'used variables' compiling warnings

(note the space after "ext4: ", the lack of a ending period, and the
spelling correction for "unsed"; the other change which I will
commonly make for folks, again for consistency, is to make the first
word after "ext4: " lower case --- the summary does not have to be a
complete sentence, which is why I remove the trailing period)

Thanks,

						- Ted

  reply	other threads:[~2011-06-27 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15  3:27 [PATCH] ext4:quiet 'unsed variables' compiling warnings Yongqiang Yang
2011-06-27 20:34 ` Ted Ts'o [this message]
2011-06-28  1:32   ` Yongqiang Yang

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=20110627203442.GF2729@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=xiaoqiangnk@gmail.com \
    /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.