From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,T_DKIMWL_WL_HIGH,UNPARSEABLE_RELAY,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CB078C04AB6 for ; Tue, 28 May 2019 08:36:17 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 9FDDF208C3 for ; Tue, 28 May 2019 08:36:17 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="hkoqtbu6" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9FDDF208C3 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=collabora.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date: Message-ID:From:References:To:Subject:Reply-To:Content-ID:Content-Description :Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=0L4By4FQjrTrATO+ZfqYJwk3K6X99rNlzkTk+69muLM=; b=hkoqtbu6oBKxF1 cXMVCsTpoYsllQxrhFCMsbQhFMb3L4gNhOX8BpkGcEeOyQwIEH9euRc20vf3/ibGDUkZ5zpWdCeOu /SlE6zHlKsAWSXIZMWTLZUQCReieOEFF1SQZeNY9ww2KZHOb+tbHJkELiW8BuS9U+EhwSIuO+qk6G E2SL370beDVIBH1AS4IzKmswLu91kvwq8T++01cV/tSaotMJyu6FC74WH/3fB7MTXz2zMGJkdklHd wMZCsgKBaVB9PKvfAYkqGmL1EsLcPW9EFWzQvgn6/7wdpr6qdTFoiEaSdabHirPgtSrCUaoUEZ+Wa Um0uLpmyWyDo46WvU/iw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hVXad-00018X-Du; Tue, 28 May 2019 08:36:11 +0000 Received: from bhuna.collabora.co.uk ([46.235.227.227]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hVXaa-00017s-Bc; Tue, 28 May 2019 08:36:10 +0000 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: gtucker) with ESMTPSA id 603D727FF5B Subject: Re: linusw/for-next boot bisection: v5.2-rc1-8-g73a790c68d7e on rk3288-veyron-jaq To: Geert Uytterhoeven References: <5cec74e8.1c69fb81.37335.9d7b@mx.google.com> <0edab48f-06e5-9ed8-09be-7c9976ae1afb@collabora.com> From: Guillaume Tucker Message-ID: Date: Tue, 28 May 2019 09:36:03 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190528_013608_663496_7E3F110E X-CRM114-Status: GOOD ( 14.69 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Daniel Lezcano , Heiko Stuebner , Tomeu Vizoso , Linux PM list , Kevin Hilman , Linus Walleij , Elaine Zhang , Linux Kernel Mailing List , Eduardo Valentin , "open list:ARM/Rockchip SoC..." , Mark Brown , Matt Hart , mgalka@collabora.com, Enric Balletbo i Serra , Zhang Rui , Linux ARM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Geert, On 28/05/2019 08:45, Geert Uytterhoeven wrote: > Hi Guillaume, > > On Tue, May 28, 2019 at 9:13 AM Guillaume Tucker > wrote: >> On 28/05/2019 00:38, kernelci.org bot wrote: >>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * >>> * This automated bisection report was sent to you on the basis * >>> * that you may be involved with the breaking commit it has * >>> * found. No manual investigation has been done to verify it, * >>> * and the root cause of the problem may be somewhere else. * >>> * Hope this helps! * >>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * >>> >>> linusw/for-next boot bisection: v5.2-rc1-8-g73a790c68d7e on rk3288-veyron-jaq >>> >>> Summary: >>> Start: 73a790c68d7e Merge branch 'devel' into for-next >>> Details: https://kernelci.org/boot/id/5cebf03d59b514dd627a3629 >>> Plain log: https://storage.kernelci.org//linusw/for-next/v5.2-rc1-8-g73a790c68d7e/arm/multi_v7_defconfig/gcc-8/lab-collabora/boot-rk3288-veyron-jaq.txt >>> HTML log: https://storage.kernelci.org//linusw/for-next/v5.2-rc1-8-g73a790c68d7e/arm/multi_v7_defconfig/gcc-8/lab-collabora/boot-rk3288-veyron-jaq.html >>> Result: 28694e009e51 thermal: rockchip: fix up the tsadc pinctrl setting error >>> >>> Checks: >>> revert: PASS >>> verify: PASS >>> >>> Parameters: >>> Tree: linusw >>> URL: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/ >>> Branch: for-next >>> Target: rk3288-veyron-jaq >>> CPU arch: arm >>> Lab: lab-collabora >>> Compiler: gcc-8 >>> Config: multi_v7_defconfig >>> Test suite: boot >>> >>> Breaking commit found: >>> >>> ------------------------------------------------------------------------------- >>> commit 28694e009e512451ead5519dd801f9869acb1f60 >>> Author: Elaine Zhang >>> Date: Tue Apr 30 18:09:44 2019 +0800 >>> >>> thermal: rockchip: fix up the tsadc pinctrl setting error >> >> This commit has now been reverted in mainline. Would it be OK >> for you to rebase your for-next branch on v5.2-rc2 or cherry-pick >> the revert to avoid recurring bisections? >> >> Ideally this should have been fixed or reverted in mainline >> before v5.2-rc1 was released, or even earlier when this was first >> found in -next on 13th May. Unfortunately it was overlooked and >> then spread to other branches like yours. > > I'm afraid it's gonna spread to even more for-next branches, as most > subsystem maintainers base their for-next branch on the previous rc1 > release. Typically maintainers do not rebase their for-next branches, > and do not cherry-pick fixes, unless they are critical for their > subsystem. So you can expect this to show up in e.g. the m68k for-next > branch soon... That is what I feared, thanks for confirming. > Can't you mark this as a known issue, to prevent spending cycles on the > same bisection, and sending out more bisection reports for the same > issue? Not really, so I've disabled bisections in the linux-gpio tree and a few other maintainers' trees for now. I'll see if we can come up with a more systematic way of suppressing bisections in similar cases (i.e. the issue has been fixed in mainline later than the base commit for the branch being tested). Thanks, Guillaume _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel