[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130327083535.22ef6a9046f4b53e161481de@canb.auug.org.au>
Date: Wed, 27 Mar 2013 08:35:35 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Kent Overstreet <koverstreet@...gle.com>,
Jens Axboe <axboe@...nel.dk>, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: linux-next: build warning after merge of the final tree (akpm
and block tree related)
Hi Guys,
On Tue, 26 Mar 2013 13:10:51 -0700 Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Tue, 26 Mar 2013 12:55:23 -0700 Kent Overstreet <koverstreet@...gle.com> wrote:
>
> > On Tue, Mar 26, 2013 at 05:05:54PM +1100, Stephen Rothwell wrote:
> > >
> > > 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.
Yeah, though a hint might be nice. It looks like these completion
routines just need the batch argument added, right?
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists