[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230926131339.nigj6gp35r74yban@dhruva>
Date: Tue, 26 Sep 2023 18:43:39 +0530
From: Dhruva Gole <d-gole@...com>
To: Mark Brown <broonie@...nel.org>
CC: <linux-spi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Vignesh Raghavendra <vigneshr@...com>,
kernel test robot <lkp@...el.com>,
Dan Carpenter <dan.carpenter@...aro.org>
Subject: Re: [PATCH V2] spi: spi-cadence-quadspi: Fix missing unwind goto
warnings
On Sep 26, 2023 at 14:48:27 +0200, Mark Brown wrote:
> On Tue, Sep 26, 2023 at 05:49:08PM +0530, Dhruva Gole wrote:
>
> > 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?
>
> Including a full 12 character commit hash would help with matching,
I have given the full 12 chars, else checkpatch would've caught me :)
> there were only 10 there. Not mix'n'matching Link:/Close: with links in
> the body of the commit message would help as well.
OK, I have fixed the links and sent the patch V3
Again, I have based on your for-next, as I don't see the fixes: commit in
the 6.6 tree.
--
Best regards,
Dhruva Gole <d-gole@...com>
Powered by blists - more mailing lists