linux-kernel - linux-next: build warning after merge of the akpmtree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <20130510131146.9646757173476e28de57f6aa@canb.auug.org.au>
Date:	Fri, 10 May 2013 13:11:46 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Keith Busch <keith.busch@...el.com>,
	Matthew Wilcox <matthew.r.wilcox@...el.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Kent Overstreet <koverstreet@...gle.com>
Subject: linux-next: build warning after merge of the akpmtree

Hi Andrew,

After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:

drivers/block/nvme-core.c: In function 'nvme_bio_split':
/scratch/sfr/next/drivers/block/nvme-core.c:483:19: warning: assignment from incompatible pointer type [enabled by default]
/scratch/sfr/next/drivers/block/nvme-core.c:484:19: warning: assignment from incompatible pointer type [enabled by default]

Introduced by commit 427e97080196 ("NVMe: Split non-mergeable bio
requests") from Linus' tree interacting with commit 6a4d55146334 ("block:
prep work for batch completion") from the akpm tree.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped