From: Andrew Morton <akpm@linux-foundation•org>
To: Kent Overstreet <koverstreet@google•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Jens Axboe <axboe@kernel•dk>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: build warning after merge of the final tree (akpm and block tree related)
Date: Tue, 26 Mar 2013 13:10:51 -0700 [thread overview]
Message-ID: <20130326131051.a47fe83fdbdab4b824394f18@linux-foundation.org> (raw)
In-Reply-To: <20130326195523.GB24935@google.com>
On Tue, 26 Mar 2013 12:55:23 -0700 Kent Overstreet <koverstreet@google•com> wrote:
> On Tue, Mar 26, 2013 at 05:05:54PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the final tree, today's linux-next build
> > produced this warning:
> >
> > fs/bio.c: In function 'submit_bio_wait':
> > fs/bio.c:786:17: warning: assignment from incompatible pointer type [enabled by default]
> >
> > This is due to an interaction between commit 9e882242c ("block: Add
> > submit_bio_wait(), remove from md") from the block tree and commit
> > "block: prep work for batch completion" from the akpm tree.
>
> In hindsight maybe it would've been better if the batch completion stuff
> had gone in via Jens' tree, though I'm sure there would've still been
> some conflicts.
>
> What's the procedure for me to fix these? I can send you a fixup patch
> but if you've pushed this version of linux-next somewhere public I'm not
> sure where to look.
Stephen and I quietly fix up this sort of thing.
next prev parent reply other threads:[~2013-03-26 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 6:05 linux-next: build warning after merge of the final tree (akpm and block tree related) Stephen Rothwell
2013-03-26 19:55 ` Kent Overstreet
2013-03-26 20:10 ` Andrew Morton [this message]
2013-03-26 21:35 ` Stephen Rothwell
2013-03-26 21:43 ` Andrew Morton
2013-03-26 22:05 ` Stephen Rothwell
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=20130326131051.a47fe83fdbdab4b824394f18@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=axboe@kernel$(echo .)dk \
--cc=koverstreet@google$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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