linux-kernel - Re: linux-next: build failure after merge of the device-mapper tree

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100802113407.GF9734@agk-dp.fab.redhat.com>
Date:	Mon, 2 Aug 2010 12:34:07 +0100
From:	Alasdair G Kergon <agk@...hat.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Milan Broz <mbroz@...hat.com>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the device-mapper tree

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/