linux-next: build failure after merge of the device-mapper tree
in [Kernel]
|
Prev: [PATCH 02/19] perf sort: Make column width code per hists instance
Next: drivers/scsi/pm8001: introduce missing kfree
From: Stephen Rothwell on 1 Aug 2010 21:40 Hi Alasdair, After merging the device-mapper tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/md/dm-crypt.c: In function 'crypt_ctr_cipher': drivers/md/dm-crypt.c:1095: error: 'bad_mem' undeclared (first use in this function) Caused by commit 460328b294ddd132945bdf536a9130f2d6cd6ace ("dm-crypt-simplify-crypt_ctr"). Please do test builds ... "No functional change in this patch." :-( I will use the device-mapper tree from next-20100730 for today. P.S. the patch summaries could be more informative ... i.e. you should put "Subject:" lines in the patches. -- Cheers, Stephen Rothwell sfr(a)canb.auug.org.au http://www.canb.auug.org.au/~sfr/
From: Milan Broz on 2 Aug 2010 02:50 On 08/02/2010 03:31 AM, Stephen Rothwell wrote: > After merging the device-mapper tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > drivers/md/dm-crypt.c: In function 'crypt_ctr_cipher': > drivers/md/dm-crypt.c:1095: error: 'bad_mem' undeclared (first use in this function) hmmmm, Alasdair you edited that patch? The version I sent compiled cleanly. (moreover it is just part of patchset which is not yet fully there, seems) Milan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Alasdair G Kergon on 2 Aug 2010 07:40
On Mon, Aug 02, 2010 at 11:31:48AM +1000, Stephen Rothwell wrote: > I will use the device-mapper tree from next-20100730 for today. Gah - I forgot to repush it, sorry. Milan - I made it so the inner function always sets an error message, instead of making the caller have a special case to detect whether or not it had been set. > P.S. the patch summaries could be more informative ... i.e. you should > put "Subject:" lines in the patches. They are the quilt filenames and the subject line gets generated automatically from that when I import into git to submit to Linus. Alasdair -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |