From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rodolfo Giometti <giometti@enneenne.com>, linux-kernel@vger.kernel.org
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Eric Fourmont <eric.fourmont-ext@st.com>,
Yann GAUTIER <yann.gautier@foss.st.com>
Subject: Re: [V1 1/2] arm stm32mp131.dtsi: add "encoding_mode" nvmem definition
Date: Mon, 19 May 2025 20:36:55 +0200 [thread overview]
Message-ID: <020b9602-7411-44ad-889c-e8efaccac0a3@kernel.org> (raw)
In-Reply-To: <192d4c26-3733-4818-8dc1-43d736fdbf75@kernel.org>
On 19/05/2025 20:35, Krzysztof Kozlowski wrote:
> On 19/05/2025 15:08, Rodolfo Giometti wrote:
>> This patch adds the definition for the nvmem location "encoding_mode"
>
> Please do not use "This commit/patch/change", but imperative mood. See
> longer explanation here:
> https://elixir.bootlin.com/linux/v5.17.1/source/Documentation/process/submitting-patches.rst#L95
>
... and please use standard email subjects, so with the PATCH keyword in
the title. `git format-patch -vX` helps here to create proper versioned
patches. Another useful tool is b4. Skipping the PATCH keyword makes
filtering of emails more difficult thus making the review process less
convenient.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-19 18:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 13:08 [V1 0/2] Add SoC support for stm32mp13xx CPUs Rodolfo Giometti
2025-05-19 13:08 ` [V1 1/2] arm stm32mp131.dtsi: add "encoding_mode" nvmem definition Rodolfo Giometti
2025-05-19 18:35 ` Krzysztof Kozlowski
2025-05-19 18:36 ` Krzysztof Kozlowski [this message]
2025-05-20 8:26 ` Yann Gautier
2025-05-20 16:29 ` Yann Gautier
2025-05-19 13:08 ` [V1 2/2] drivers soc: add support for ST stm32mp13xx family Rodolfo Giometti
2025-05-19 18:34 ` Krzysztof Kozlowski
2025-05-20 9:01 ` Rodolfo Giometti
2025-05-20 9:15 ` Krzysztof Kozlowski
2025-05-20 8:55 ` Alexandre TORGUE
2025-05-26 10:56 ` Rodolfo Giometti
2025-05-20 16:58 ` Yann Gautier
2025-05-21 15:44 ` Rodolfo Giometti
2025-05-21 16:37 ` Krzysztof Kozlowski
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=020b9602-7411-44ad-889c-e8efaccac0a3@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=eric.fourmont-ext@st.com \
--cc=giometti@enneenne.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=yann.gautier@foss.st.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®