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] spi: spi-cadence-quadspi: Fix missing unwind goto warnings
Date: Fri, 15 Sep 2023 13:49:23 +0100 [thread overview]
Message-ID: <b22f9e16-1c65-4a9d-b3ea-9f6571647923@sirena.org.uk> (raw)
In-Reply-To: <20230915123103.2493640-1-d-gole@ti.com>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
On Fri, Sep 15, 2023 at 06:01:04PM +0530, Dhruva Gole wrote:
> Fix the smatch warnings that were recently introduced in the runtime pm
> patch [0]:
> drivers/spi/spi-cadence-quadspi.c:1882 cqspi_probe() warn: missing
> unwind goto?
>
> [0] https://lore.kernel.org/all/20230829062706.786637-1-d-gole@ti.com/
Please use normal fixes tags for things like this and in general
please include human readable descriptions of things like commits and
issues being discussed in e-mail in your mails, this makes them much
easier for humans to read especially when they have no internet access.
I do frequently catch up on my mail on trains or flights, or while
otherwise travelling so this is even more pressing for me than just
being about making things a bit easier to read.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-09-15 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 12:31 [PATCH] spi: spi-cadence-quadspi: Fix missing unwind goto warnings Dhruva Gole
2023-09-15 12:49 ` Mark Brown [this message]
2023-09-15 14:29 ` Dhruva Gole
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=b22f9e16-1c65-4a9d-b3ea-9f6571647923@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.