Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754221AbbK3VBV (ORCPT ); Mon, 30 Nov 2015 16:01:21 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:49443 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751587AbbK3VBT (ORCPT ); Mon, 30 Nov 2015 16:01:19 -0500 Date: Mon, 30 Nov 2015 15:01:17 -0600 From: Andy Gross To: Bjorn Andersson Cc: Kevin Hilman , Bjorn Andersson , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , lkml , Tyler Baker , Olof Johansson , Arnd Bergmann Subject: Re: [PATCH 1/7] ARM: dts: qcom: msm8974-honami: Define pinctrl state for blsp_uart2 Message-ID: <20151130210117.GA14162@Agamemnon.attlocal.net> References: <1445403470-17434-1-git-send-email-bjorn.andersson@sonymobile.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1660 Lines: 36 On Mon, Nov 30, 2015 at 12:19:13PM -0800, Bjorn Andersson wrote: > On Mon, Nov 30, 2015 at 11:23 AM, Kevin Hilman wrote: > > On Tue, Oct 20, 2015 at 9:57 PM, Bjorn Andersson > > wrote: > >> Make sure the blsp1_uart2 pins are in the correct state for the uart. > >> > >> Signed-off-by: Bjorn Andersson > > > > kernelci.org has been detecting boot failures on my z1 since > > next-20151120[1] and I finally got around to bisecting, which pointed > > to this patch which is in next in the for of commit 14cd83b824aa ARM: > > dts: qcom: msm8974-honami: Define pinctrl state for blsp_uart2 > > > > That commit doesn't revert cleanly on top of next-20151130, but > > manually removing the stuff added in this patch, next-20151130 boots > > fine on the z1. > > > > Kevin > > > > [1] http://kernelci.org/boot/qcom-msm8974-sony-xperia-honami/job/next/kernel/next-20151127/defconfig/multi_v7_defconfig/lab/lab-khilman/?_id=5658061359b5140196b5fd2f > > Thanks Kevin, > > I did see these too. But at the same time, as far as I can see, the > qcom_defconfig boots just fine - indicating that this particular > commit would not be the cause. > > I'll fire up some builds to figure out what's going on. I threw the extra config options that qcom_defconfig had on it on top of my next branch. I hadn't seen any kernel ci runs on that yet. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/