From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, wenqing.lz@taobao.com
Subject: Re: [PATCH 1/2] ext4: fix usless declarations
Date: Wed, 03 Apr 2013 16:31:23 +0400 [thread overview]
Message-ID: <878v4zre1w.fsf@openvz.org> (raw)
In-Reply-To: <20130403122641.GC7741@thunk.org>
On Wed, 3 Apr 2013 08:26:41 -0400, Theodore Ts'o <tytso@mit.edu> wrote:
> On Wed, Apr 03, 2013 at 02:58:30PM +0400, Dmitry Monakhov wrote:
> > This patch should fix sparse complains about shadow declatations.
>
> Nothing here is fixing serious regressions, right? This is just to
> make static code checkers happy?
Yep... but fixes are also quite simple.
>
> - Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-04-03 12:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 10:58 [PATCH 1/2] ext4: fix usless declarations Dmitry Monakhov
2013-04-03 10:58 ` [PATCH 2/2] ext4: fix cpu_vs_disk conversions Dmitry Monakhov
2013-04-03 12:33 ` Theodore Ts'o
2013-04-03 12:58 ` Dmitry Monakhov
2013-04-03 13:04 ` Zheng Liu
2013-04-03 16:01 ` Theodore Ts'o
2013-04-03 15:37 ` Theodore Ts'o
2013-04-03 15:55 ` Dmitry Monakhov
2013-04-04 14:42 ` Dmitry Monakhov
2013-04-10 4:01 ` Theodore Ts'o
2013-04-10 4:02 ` [PATCH 1/3] ext4: fix big-endian bug in extent migration code Theodore Ts'o
2013-04-10 4:02 ` [PATCH 2/3] ext4: fix big-endian bug in metadata checksum calculations Theodore Ts'o
2013-04-10 4:02 ` [PATCH 3/3] ext4: fix miscellaneous big endian warnings Theodore Ts'o
2013-04-03 12:26 ` [PATCH 1/2] ext4: fix usless declarations Theodore Ts'o
2013-04-03 12:31 ` Dmitry Monakhov [this message]
2013-04-10 2:50 ` [1/2] " Theodore Ts'o
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=878v4zre1w.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wenqing.lz@taobao.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 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).