From: "Jörn Engel" <joern@logfs.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: linux-next: vfs tree build warning
Date: Mon, 18 Jan 2010 15:34:15 +0100 [thread overview]
Message-ID: <20100118143415.GA5700@logfs.org> (raw)
In-Reply-To: <20100118131128.a09d1021.sfr@canb.auug.org.au>
On Mon, 18 January 2010 13:11:28 +1100, Stephen Rothwell wrote:
>
> Today's linux-next build (x86_64_allmodconfig) produced this warning:
>
> fs/logfs/inode.c:399: warning: initialization from incompatible pointer type
>
> Introduced by commit bc39e28236344af617473df80abb7de43176511e ("pass
> writeback_control to ->write_inode") from the vfs tree interacting with
> commit 5db53f3e80dee2d9dff5e534f9e9fe1db17c9936 ("[LogFS] add new flash
> file system") from the logfs tree.
>
> This will need a fixup patch (see below) which I can carry in the
> linux-next tree. There may, of course, be a better fix (which I can
> carry if someone sends it to me).
Looks good enough for me for now. Next week, after returning from
vacation, I'll have a closer look and update the logfs tree.
Thank you, Stephen!
Jörn
--
Joern's library part 7:
http://www.usenix.org/publications/library/proceedings/neworl/full_papers/mckusick.a
next prev parent reply other threads:[~2010-01-18 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 2:11 linux-next: vfs tree build warning Stephen Rothwell
2010-01-18 14:34 ` Jörn Engel [this message]
2010-01-18 23:43 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2010-01-18 2:11 Stephen Rothwell
2010-01-18 4:34 ` Sage Weil
2010-01-18 5:41 ` Stephen Rothwell
2010-01-18 6:01 ` Al Viro
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=20100118143415.GA5700@logfs.org \
--to=joern@logfs.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@ZenIV.linux.org.uk \
/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