All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Dhruva Gole <d-gole@ti.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Vignesh Raghavendra <vigneshr@ti.com>,
	kernel test robot <lkp@intel.com>,
	Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH V2] spi: spi-cadence-quadspi: Fix missing unwind goto warnings
Date: Tue, 26 Sep 2023 14:48:27 +0200	[thread overview]
Message-ID: <ZRLTG4pogXW5FTgJ@finisterre.sirena.org.uk> (raw)
In-Reply-To: <20230926121908.mcyyj42buqr4ov3m@dhruva>

[-- Attachment #1: Type: text/plain, Size: 439 bytes --]

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,
there were only 10 there.  Not mix'n'matching Link:/Close: with links in
the body of the commit message would help as well.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-09-26 12:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19  7:46 [PATCH V2] spi: spi-cadence-quadspi: Fix missing unwind goto warnings Dhruva Gole
2023-09-21 12:03 ` Dan Carpenter
2023-09-26 11:21 ` Mark Brown
2023-09-26 11:34   ` Dhruva Gole
2023-09-26 11:40   ` Dhruva Gole
2023-09-26 11:58     ` Mark Brown
2023-09-26 12:19       ` Dhruva Gole
2023-09-26 12:48         ` Mark Brown [this message]
2023-09-26 13:13           ` Dhruva Gole
2023-09-26 15:07 ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZRLTG4pogXW5FTgJ@finisterre.sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=d-gole@ti.com \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.