From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alasdair G Kergon Subject: Re: linux-next: build failure after merge of the device-mapper tree Date: Mon, 2 Aug 2010 12:34:07 +0100 Message-ID: <20100802113407.GF9734@agk-dp.fab.redhat.com> References: <20100802113148.e0b70b34.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx1.redhat.com ([209.132.183.28]:46543 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752246Ab0HBLeN (ORCPT ); Mon, 2 Aug 2010 07:34:13 -0400 Content-Disposition: inline In-Reply-To: <20100802113148.e0b70b34.sfr@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell , Milan Broz Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org 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