From: Mark Brown <broonie@kernel.org>
To: Randy Li <ayaka@soulik.info>
Cc: alsa-devel@alsa-project.org, sbkim73@samsung.com,
s.nawrocki@samsung.com, lgirdwood@gmail.com, perex@perex.cz,
tiwai@suse.com, krzk@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] make samsung interface entries explicitly
Date: Mon, 19 Sep 2016 09:33:01 +0100 [thread overview]
Message-ID: <20160919083301.GD10189@sirena.org.uk> (raw)
In-Reply-To: <1474207751-9804-1-git-send-email-ayaka@soulik.info>
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
On Sun, Sep 18, 2016 at 10:09:10PM +0800, Randy Li wrote:
> I found those modules should be selected directly, as I
> only use the simple sound card.
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: 473 bytes --]
prev parent reply other threads:[~2016-09-19 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 14:09 [PATCH] make samsung interface entries explicitly Randy Li
2016-09-18 14:09 ` [PATCH] ASoC: samsung: make audio interface/controller explicitly Randy Li
2016-09-18 14:42 ` Krzysztof Kozlowski
2016-09-18 15:12 ` ayaka
2016-09-18 18:09 ` Krzysztof Kozlowski
2016-09-19 1:21 ` Ayaka
2016-09-19 15:15 ` Krzysztof Kozlowski
2016-09-18 17:27 ` kbuild test robot
2016-09-19 1:42 ` kbuild test robot
2016-09-19 8:33 ` Mark Brown
2016-09-19 9:41 ` Ayaka
2016-09-19 10:23 ` Mark Brown
2016-09-19 8:33 ` Mark Brown [this message]
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=20160919083301.GD10189@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ayaka@soulik.info \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=perex@perex.cz \
--cc=s.nawrocki@samsung.com \
--cc=sbkim73@samsung.com \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).