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=-5.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no 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 77331C4363D for ; Fri, 2 Oct 2020 14:40:25 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (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 26DDA206B2 for ; Fri, 2 Oct 2020 14:40:25 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="ICP8E5fe" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 26DDA206B2 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=arm.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+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=merlin.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:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=Ztk/9FWjL+RmoT67LhA4vfWz3sCP+HdJZWCAO2yBSiU=; b=ICP8E5fe52q/6LWf/tAQR6EvP O5ghPt6RnPZsn4UqmhVwyKyNbCHZuvL6CE0dyD3uSU2PM5pkzecLJj2E4lz2r7zav5FueD8guEGfh O6nlGLRnB1996fxUPP9bmzhotiTLMJ33ylZu/4x/zVRGK2gQpFI98Cs2STrRqQAJicMgpbphsybOb bnQEjyr8FP79q2BaxH/nEhz+hcWMRQqs5UL63TLDGju8dXgUNdORURThVfA2T9VeolIEucMrjdLQX xBWFVVVsuVbYwY3Z9l7858FW+17jEtn2d/9w2bDTQdLT5mkdILmHePi9SntVfTeKNT+ovVjf9CUJ8 PVuAxrGnw==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kOMDE-0004Qj-P3; Fri, 02 Oct 2020 14:39:08 +0000 Received: from foss.arm.com ([217.140.110.172]) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kOMDA-0004PL-TW for linux-arm-kernel@lists.infradead.org; Fri, 02 Oct 2020 14:39:06 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 3C64D30E; Fri, 2 Oct 2020 07:38:58 -0700 (PDT) Received: from e121166-lin.cambridge.arm.com (e121166-lin.cambridge.arm.com [10.1.196.255]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id C518C3F70D; Fri, 2 Oct 2020 07:38:56 -0700 (PDT) Date: Fri, 2 Oct 2020 15:38:51 +0100 From: Lorenzo Pieralisi To: Pali =?iso-8859-1?Q?Roh=E1r?= Subject: Re: [PATCH 0/2] PCI: aardvark: Fix comphy with old ATF Message-ID: <20201002143851.GA25575@e121166-lin.cambridge.arm.com> References: <20200902144344.16684-1-pali@kernel.org> <20201002133713.GA24425@e121166-lin.cambridge.arm.com> <20201002142616.dxgdneg2lqw4pxie@pali> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20201002142616.dxgdneg2lqw4pxie@pali> User-Agent: Mutt/1.9.4 (2018-02-28) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201002_103905_011068_441700CC X-CRM114-Status: GOOD ( 23.77 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Tomasz Maciej Nowak , Rob Herring , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Kishon Vijay Abraham I , Vinod Koul , Miquel Raynal , Bjorn Helgaas , Marek =?iso-8859-1?Q?Beh=FAn?= , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Oct 02, 2020 at 04:26:16PM +0200, Pali Roh=E1r wrote: > On Friday 02 October 2020 14:37:13 Lorenzo Pieralisi wrote: > > On Wed, Sep 02, 2020 at 04:43:42PM +0200, Pali Roh=E1r wrote: > > > This patch series fixes regression introduced in commit 366697018c9a > > > ("PCI: aardvark: Add PHY support") which caused aardvark driver > > > initialization failure on EspressoBin board with factory version of > > > Arm Trusted Firmware provided by Marvell. > > > = > > > Second patch depends on the first patch, so please add appropriate > > > Fixes/Cc:stable@ tags to have both patches correctly backported to > > > stable kernels. > > > = > > > I have tested both patches with Marvell ATF firmware ebin-17.10-uart.= zip > > > and with upstream ATF+uboot and aardvark was initialized successfully. > > > Without this patch series on ebin-17.10-uart.zip aardvark initializat= ion > > > failed. > > > = > > > Pali Roh=E1r (2): > > > phy: marvell: comphy: Convert internal SMCC firmware return codes to > > > errno > > > PCI: aardvark: Fix initialization with old Marvell's Arm Trusted > > > Firmware > > > = > > > drivers/pci/controller/pci-aardvark.c | 4 +++- > > > drivers/phy/marvell/phy-mvebu-a3700-comphy.c | 14 +++++++++++--- > > > drivers/phy/marvell/phy-mvebu-cp110-comphy.c | 14 +++++++++++--- > > > 3 files changed, 25 insertions(+), 7 deletions(-) > > = > > Applied to pci/aardvark (both patches), thanks. > = > Ok! For second patch would be needed to put CC:stable line with > specifying prerequisite of first patch as written in document: > = > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html > = > If I understood it correctly, second patch needs following line: > = > Cc: # : comphy: errno r= eturn codes > = > where is commit id of PATCH 1/2. > = > (correct me if I'm wrong) > = > Now when first commit has commit id, could you update second commit to > include this information about prerequisite? No I can't because they will be merged at the same time. What we can do is mark the second patch for stable and during the stable review ask to pull patch (1). Or better you shall send both patches to stable kernels when they hit Linus' tree. Lorenzo _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel