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 [email protected]
http://www.canb.auug.org.au/~sfr/
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
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