From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Gross Subject: Re: linux-next: build failure after merge of the qcom tree Date: Thu, 26 Apr 2018 16:23:30 -0500 Message-ID: <20180426212330.GD25699@hector.attlocal.net> References: <20180426084041.5cf81918@canb.auug.org.au> <20180426145255.0141300e@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Evan Green Cc: sfr@canb.auug.org.au, agross@codeaurora.org, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Karthikeyan Ramasubramanian , Sagar Dharia , Girish Mahadevan , groeck@chromium.org List-Id: linux-next.vger.kernel.org On Thu, Apr 26, 2018 at 04:42:17PM +0000, Evan Green wrote: > > I suspect that just Linus' tree merged with the qcom tree would have > > been enough to cause the failure. Sorry for missing this in my testing. > > > I've verified that the patch listed above fixes the issue for me. Andy, if > it looks okay to you, go ahead an pull it in. Apologies for the trouble, > and thanks Guenter for having builders that notice this stuff early! > -Evan Thanks for looking at this Evan. Andy