From: "Jörn Engel" <joern@logfs.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the logfs tree
Date: Sat, 8 May 2010 14:32:00 +0200 [thread overview]
Message-ID: <20100508123200.GD21185@logfs.org> (raw)
In-Reply-To: <20100507094638.11351234.sfr@canb.auug.org.au>
On Fri, 7 May 2010 09:46:38 +1000, Stephen Rothwell wrote:
>
> After merging the logfs tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> fs/logfs/file.c: In function 'logfs_fsync':
> fs/logfs/file.c:225: warning: unused variable 'super'
>
> Introduced by commit c0c79c31c9d5fcc19812c6c35f842baf50ee788a ("logfs:
> fix sync").
Thanks, fixed.
Jörn
--
The grand essentials of happiness are: something to do, something to
love, and something to hope for.
-- Allan K. Chalmers
prev parent reply other threads:[~2010-05-08 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 23:46 linux-next: build warning after merge of the logfs tree Stephen Rothwell
2010-05-08 12:32 ` Jörn Engel [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=20100508123200.GD21185@logfs.org \
--to=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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