From: Jerome Brunet <jbrunet@baylibre.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-amlogic@lists.infradead.org,
Kevin Hilman <khilman@baylibre.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/1] ASoC: dt-bindings: meson: covert axg audio to schema
Date: Wed, 08 Feb 2023 14:25:58 +0100 [thread overview]
Message-ID: <1j4jrwmghi.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <Y+OJB7OPABnPfeq7@sirena.org.uk>
On Wed 08 Feb 2023 at 11:35, Mark Brown <broonie@kernel.org> wrote:
> [[PGP Signed Part:Undecided]]
> On Wed, Feb 08, 2023 at 10:35:18AM +0100, Jerome Brunet wrote:
>> Continue conversion of AXG audio dt-binding documentation to schema
>
> Please don't send cover letters for single patches, if there is anything
> that needs saying put it in the changelog of the patch or after the ---
> if it's administrative stuff. This reduces mail volume and ensures that
> any important information is recorded in the changelog rather than being
> lost.
I usually don't send cover-letter for single patches.
This was originally a 9 patches series and it dropped to a single one as
you applied them. I was wondering wether to keep the cover-letter or
not. I thought keeping it might be better to keep track of the series.
If the same case happen again, I'll skip the cover-letter.
>
> [[End of PGP Signed Part]]
next prev parent reply other threads:[~2023-02-08 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 9:35 [PATCH v3 0/1] ASoC: dt-bindings: meson: covert axg audio to schema Jerome Brunet
2023-02-08 9:35 ` [PATCH v3 1/1] ASoC: dt-bindings: meson: convert axg sound card control " Jerome Brunet
2023-02-08 10:11 ` Krzysztof Kozlowski
2023-02-08 11:35 ` [PATCH v3 0/1] ASoC: dt-bindings: meson: covert axg audio " Mark Brown
2023-02-08 13:25 ` Jerome Brunet [this message]
2023-02-08 18:21 ` 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=1j4jrwmghi.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
/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