From: Mark Brown <broonie@kernel.org>
To: Ariel D'Alessandro <ariel.dalessandro@collabora.com>
Cc: alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, Xiubo.Lee@gmail.com,
bcousson@baylibre.com, festevam@gmail.com,
kuninori.morimoto.gx@renesas.com, lgirdwood@gmail.com,
michael@amarulasolutions.com, nicoleotsuka@gmail.com,
perex@perex.cz, robh+dt@kernel.org, shengjiu.wang@gmail.com,
tiwai@suse.com, tony@atomide.com
Subject: Re: [PATCH 1/1] ASoC: fsl-asoc-card: Add missing Kconfig option for tlv320aic31xx
Date: Fri, 3 Dec 2021 18:11:00 +0000 [thread overview]
Message-ID: <YapdtAAbrhJ8kW0M@sirena.org.uk> (raw)
In-Reply-To: <20211203175018.252641-1-ariel.dalessandro@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 556 bytes --]
On Fri, Dec 03, 2021 at 02:50:17PM -0300, Ariel D'Alessandro wrote:
> This is a follow up of patchsets:
>
> [RFC patch 0/5] Support BCLK input clock in tlv320aic31xx
> [PATCH 0/4] fsl-asoc-card: Add optional dt property for setting mclk-id
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-12-03 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 17:50 [PATCH 1/1] ASoC: fsl-asoc-card: Add missing Kconfig option for tlv320aic31xx Ariel D'Alessandro
2021-12-03 17:50 ` Ariel D'Alessandro
2021-12-03 18:11 ` Mark Brown [this message]
2021-12-06 18:00 ` 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=YapdtAAbrhJ8kW0M@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=ariel.dalessandro@collabora.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@amarulasolutions.com \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=shengjiu.wang@gmail.com \
--cc=tiwai@suse.com \
--cc=tony@atomide.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