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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8EA3AE7E62E for ; Tue, 26 Sep 2023 12:19:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234567AbjIZMT0 (ORCPT ); Tue, 26 Sep 2023 08:19:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56062 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233899AbjIZMTZ (ORCPT ); Tue, 26 Sep 2023 08:19:25 -0400 Received: from fllv0016.ext.ti.com (fllv0016.ext.ti.com [198.47.19.142]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D0A9FEB; Tue, 26 Sep 2023 05:19:17 -0700 (PDT) Received: from lelv0266.itg.ti.com ([10.180.67.225]) by fllv0016.ext.ti.com (8.15.2/8.15.2) with ESMTP id 38QCJAjD007193; Tue, 26 Sep 2023 07:19:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1695730750; bh=7q2mcWowuXIseloHSNPJOl7feeh1tGeHqj6t3EOTIFk=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=Nnpp7AAhl2cWGyMx6O1xSmwlHXrEsMSGapez22vj47dc1rNb49L+vHBtc7u28mOHZ WysxejDbCuVBVyzSHCJ48XbyX/VPTvjZ9fRTS7aIoM29FkiZdx+1FphZPP12eS+lK0 PXSKvNaVlhvBGMg3C7TMCsiuMgRLvkKdL7h7S2tI= Received: from DFLE114.ent.ti.com (dfle114.ent.ti.com [10.64.6.35]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 38QCJAWL090004 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 26 Sep 2023 07:19:10 -0500 Received: from DFLE113.ent.ti.com (10.64.6.34) by DFLE114.ent.ti.com (10.64.6.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Tue, 26 Sep 2023 07:19:10 -0500 Received: from fllv0040.itg.ti.com (10.64.41.20) by DFLE113.ent.ti.com (10.64.6.34) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Tue, 26 Sep 2023 07:19:10 -0500 Received: from localhost (ileaxei01-snat2.itg.ti.com [10.180.69.6]) by fllv0040.itg.ti.com (8.15.2/8.15.2) with ESMTP id 38QCJ9cm120901; Tue, 26 Sep 2023 07:19:09 -0500 Date: Tue, 26 Sep 2023 17:49:08 +0530 From: Dhruva Gole To: Mark Brown CC: , , Vignesh Raghavendra , kernel test robot , Dan Carpenter Subject: Re: [PATCH V2] spi: spi-cadence-quadspi: Fix missing unwind goto warnings Message-ID: <20230926121908.mcyyj42buqr4ov3m@dhruva> References: <20230919074658.41666-1-d-gole@ti.com> <20230926114046.5ukretunoud3yv45@dhruva> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sep 26, 2023 at 13:58:13 +0200, Mark Brown wrote: > On Tue, Sep 26, 2023 at 05:10:46PM +0530, Dhruva Gole wrote: > > > Pardon, which branch is this being applied on? > > It'll have been applied as a fix so against 6.6. Umm I don't think the commit being fixed is there in 6.6? I am not really sure how I should base/format the patch? Please can you tell me what's expected in such a case ideally? -- Best regards, Dhruva Gole