From: Alain Volmat <alain.volmat@foss.st.com>
To: Mark Brown <broonie@kernel.org>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
<linux-spi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/4] drivers: spi: st: use pm_ptr and remove __maybe_unused
Date: Tue, 6 Jan 2026 16:13:42 +0100 [thread overview]
Message-ID: <20260106151342.GA1667031@gnbcxd0016.gnb.st.com> (raw)
In-Reply-To: <fe48d1c2-07c4-451c-a2e7-338570557e93@sirena.org.uk>
Hi Mark,
On Tue, Jan 06, 2026 at 12:22:21PM +0000, Mark Brown wrote:
> On Tue, Jan 06, 2026 at 01:14:16PM +0100, Alain Volmat wrote:
> > Update ST related SPI drivers in order to remove the __maybe_unused
> > statements on pm related functions thanks to the usage of pm_ptr.
>
> Please submit patches using subject lines reflecting the style for the
> subsystem, this makes it easier for people to identify relevant patches.
> Look at what existing commits in the area you're changing are doing and
> make sure your subject lines visually resemble what they're doing.
> There's no need to resubmit to fix this alone.
oups, sorry I missed that indeed. Thanks for your help for this issue.
Regards,
Alain
next prev parent reply other threads:[~2026-01-06 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 12:14 Alain Volmat
2026-01-06 12:14 ` [PATCH 1/4] drivers: spi: st: remove __maybe_unused for suspend/resume Alain Volmat
2026-01-06 17:05 ` Jonathan Cameron
2026-01-06 12:14 ` [PATCH 2/4] drivers: spi: stm32-ospi: avoid __maybe_unused and use pm_ptr Alain Volmat
2026-01-06 12:14 ` [PATCH 3/4] drivers: spi: stm32-qspi: " Alain Volmat
2026-01-06 12:14 ` [PATCH 4/4] drivers: spi: stm32: " Alain Volmat
2026-01-06 12:22 ` [PATCH 0/4] drivers: spi: st: use pm_ptr and remove __maybe_unused Mark Brown
2026-01-06 15:13 ` Alain Volmat [this message]
2026-01-06 18:25 ` 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=20260106151342.GA1667031@gnbcxd0016.gnb.st.com \
--to=alain.volmat@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®