From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kent Overstreet Subject: Re: linux-next: build warning after merge of the final tree (akpm and block tree related) Date: Tue, 26 Mar 2013 12:55:23 -0700 Message-ID: <20130326195523.GB24935@google.com> References: <20130326170554.f9f113fa24a1e5ec6d5d1ee6@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-pa0-f41.google.com ([209.85.220.41]:36458 "EHLO mail-pa0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759925Ab3CZTz0 (ORCPT ); Tue, 26 Mar 2013 15:55:26 -0400 Received: by mail-pa0-f41.google.com with SMTP id kx1so1331926pab.0 for ; Tue, 26 Mar 2013 12:55:26 -0700 (PDT) Content-Disposition: inline In-Reply-To: <20130326170554.f9f113fa24a1e5ec6d5d1ee6@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Jens Axboe , Andrew Morton , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org 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. > > In fact we are getting several more warnings due to that patch in the > akpm tree: > > drivers/md/bcache/writeback.c: In function 'write_dirty': > drivers/md/bcache/writeback.c:276:20: warning: assignment from incompatible pointer type [enabled by default] > drivers/md/bcache/writeback.c: In function 'read_dirty': > drivers/md/bcache/writeback.c:350:21: warning: assignment from incompatible pointer type [enabled by default] > drivers/md/bcache/movinggc.c: In function 'read_moving': > drivers/md/bcache/movinggc.c:160:18: warning: assignment from incompatible pointer type [enabled by default] > drivers/md/bcache/request.c: In function 'bch_insert_data_loop': > drivers/md/bcache/request.c:518:16: warning: assignment from incompatible pointer type [enabled by default] > drivers/md/bcache/request.c: In function 'do_bio_hook': > drivers/md/bcache/request.c:684:18: warning: assignment from incompatible pointer type [enabled by default] > drivers/md/bcache/request.c: In function 'cached_dev_cache_miss': > drivers/md/bcache/request.c:926:19: warning: assignment from incompatible pointer type [enabled by default] > drivers/md/bcache/request.c:957:29: warning: assignment from incompatible pointer type [enabled by default] > drivers/md/bcache/debug.c: In function 'bch_data_verify': > drivers/md/bcache/debug.c:208:19: warning: assignment from incompatible pointer type [enabled by default] > drivers/md/bcache/super.c: In function 'bch_write_bdev_super': > drivers/md/bcache/super.c:257:17: warning: assignment from incompatible pointer type [enabled by default] > drivers/md/bcache/super.c: In function 'bcache_write_super': > drivers/md/bcache/super.c:295:18: warning: assignment from incompatible pointer type [enabled by default] > drivers/md/bcache/super.c: In function 'uuid_io': > drivers/md/bcache/super.c:333:18: warning: assignment from incompatible pointer type [enabled by default] > drivers/md/bcache/super.c: In function 'prio_io': > drivers/md/bcache/super.c:492:17: warning: assignment from incompatible pointer type [enabled by default] > > There are probably more ... > -- > Cheers, > Stephen Rothwell sfr@canb.auug.org.au