linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Jerome Marchand <jmarchan@redhat.com>,
	Theodore Ts'o <tytso@mit.edu>, Greg KH <gregkh@suse.de>,
	Andreas Dilger <adilger@sun.com>,
	linux-ext4@vger.kernel.org
Subject: Re: [PATCH] genhd: overlapping variable definition
Date: Mon, 11 Jan 2010 14:32:17 +0100	[thread overview]
Message-ID: <20100111133216.GH4489@kernel.dk> (raw)
In-Reply-To: <20100106154555.3dd77fe2@nehalam>

On Wed, Jan 06 2010, Stephen Hemminger wrote:
> This fixes the sparse warning:
> fs/ext4/super.c:2390:40: warning: symbol 'i' shadows an earlier one
> fs/ext4/super.c:2368:22: originally declared here
> 
> Using 'i' in a macro is dubious practice.

Indeed, applied. Thanks!

-- 
Jens Axboe


      reply	other threads:[~2010-01-11 13:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06 23:45 [PATCH] genhd: overlapping variable definition Stephen Hemminger
2010-01-11 13:32 ` Jens Axboe [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=20100111133216.GH4489@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=adilger@sun.com \
    --cc=gregkh@suse.de \
    --cc=jmarchan@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).