From: Al Viro <viro@ftp.linux.org.uk>
To: pinotj@club-internet.fr
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.6.14-rc2] ext3: fix build warning if !quota
Date: Thu, 29 Sep 2005 02:57:20 +0100 [thread overview]
Message-ID: <20050929015720.GQ7992@ftp.linux.org.uk> (raw)
In-Reply-To: <mnet1.1127958413.3944.pinotj@club-internet.fr>
On Thu, Sep 29, 2005 at 03:46:53AM +0200, pinotj@club-internet.fr wrote:
> Hi,
>
> (My first e-mail seems to be lost somewhere, here is a second try)
>
> sbi is not used if quota is not defined. This leads to a useless
> variable after preprocessing and a build warning.
>
> This moves the declaration in right place.
... and puts declaration in the middle of code.
next prev parent reply other threads:[~2005-09-29 1:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 1:46 [PATCH][2.6.14-rc2] ext3: fix build warning if !quota pinotj
2005-09-29 1:57 ` Al Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-29 2:24 pinotj
2005-09-29 10:10 ` Jan Kara
[not found] <88ee31b7050928174557572f77@mail.gmail.com>
2005-09-29 16:45 ` OGAWA Hirofumi
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=20050929015720.GQ7992@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pinotj@club-internet.fr \
/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