All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dhruva Gole <d-gole@ti.com>
To: Mark Brown <broonie@kernel.org>
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 17:10:46 +0530	[thread overview]
Message-ID: <20230926114046.5ukretunoud3yv45@dhruva> (raw)
In-Reply-To: <ZRK+oDrT4vaZ0R/G@finisterre.sirena.org.uk>

On Sep 26, 2023 at 13:21:04 +0200, Mark Brown wrote:
> On Tue, Sep 19, 2023 at 01:16:59PM +0530, Dhruva Gole wrote:
> > The following smatch warnings [0] were recently introduced:
> > 
> > drivers/spi/spi-cadence-quadspi.c:1882 cqspi_probe() warn: missing
> > unwind goto?
> 
> This doesn't apply against current code, please check and resend.

Pardon, which branch is this being applied on?

I am on the following base and it applies OK:
commit b643e6268c8f466ebb08a594b8ec8a1e2fd275a2 (spi-broonie/for-next)
Merge: 3b4e5194138b da6de6d3ecc1
Author: Mark Brown <broonie@kernel.org>
Date:   Tue Sep 26 13:08:30 2023 +0200

    Merge remote-tracking branch 'spi/for-6.7' into spi-next


origin: spi-broonie https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git


-- 
Best regards,
Dhruva Gole <d-gole@ti.com>

  parent reply	other threads:[~2023-09-26 11:40 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 [this message]
2023-09-26 11:58     ` Mark Brown
2023-09-26 12:19       ` Dhruva Gole
2023-09-26 12:48         ` Mark Brown
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=20230926114046.5ukretunoud3yv45@dhruva \
    --to=d-gole@ti.com \
    --cc=broonie@kernel.org \
    --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.