From: Mark Brown <broonie@kernel.org>
To: "Chiang, Mac" <mac.chiang@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"kai.vehmanen@linux.intel.com" <kai.vehmanen@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
"liam.r.girdwood@linux.intel.com"
<liam.r.girdwood@linux.intel.com>,
"CTLIN0@nuvoton.com" <CTLIN0@nuvoton.com>,
"Liao, Bard" <bard.liao@intel.com>,
"M R, Sathya Prakash" <sathya.prakash.m.r@intel.com>,
"Gopal, Vamshi Krishna" <vamshi.krishna.gopal@intel.com>
Subject: Re: [PATCH v2] ASoC: Intel: add sof-nau8825 machine driver
Date: Mon, 8 Nov 2021 12:56:09 +0000 [thread overview]
Message-ID: <YYkeaUfIOQZC03Cn@sirena.org.uk> (raw)
In-Reply-To: <PH0PR11MB5832F3AFC273BB4FBE0812F484919@PH0PR11MB5832.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
On Mon, Nov 08, 2021 at 10:28:22AM +0000, Chiang, Mac wrote:
> Add Mark for comments, CC: Mark Brown <broonie@kernel.org>
> Or I need to RESEND V2 with Acked-by:... in comment messages for your applying?
As documented in submitting-patches.rst please send patches to the
maintainers for the code you would like to change. The normal kernel
workflow is that people apply patches from their inboxes, if they aren't
copied they are likely to not see the patch at all and it is much more
difficult to apply patches.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-11-08 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 11:00 [PATCH v2] ASoC: Intel: add sof-nau8825 machine driver Mac Chiang
2021-11-03 16:36 ` Pierre-Louis Bossart
2021-11-08 10:28 ` Chiang, Mac
2021-11-08 12:56 ` 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=YYkeaUfIOQZC03Cn@sirena.org.uk \
--to=broonie@kernel.org \
--cc=CTLIN0@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=mac.chiang@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sathya.prakash.m.r@intel.com \
--cc=vamshi.krishna.gopal@intel.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