From: Mark Brown <broonie@kernel.org>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: tiwai@suse.de, vinod.koul@intel.com,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
clemens@ladisch.de, alsa-devel@alsa-project.org
Subject: Re: [PATCH] Revert "ASoC: core: mark SND_SOC_BYTES_EXT as deprecated"
Date: Thu, 15 Sep 2016 15:54:29 +0100 [thread overview]
Message-ID: <20160915145429.GL27974@sirena.org.uk> (raw)
In-Reply-To: <6357ad44-b194-7dfd-b3e8-938af89f4b54@sakamocchi.jp>
[-- Attachment #1.1: Type: text/plain, Size: 711 bytes --]
On Thu, Sep 15, 2016 at 11:41:43PM +0900, Takashi Sakamoto wrote:
> On Sep 15 2016 23:21, Charles Keepax wrote:
> > Although you might want to resend using Mark's kernel.org address
> > as I imagine he would be the one to apply the change and that is
> > the address he normally uses for patches.
> Oh, he uses the domain instead of linaro.org. I missed it.
> Now I add him to CC list.
As documented in SubmittingPatches 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 #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2016-09-15 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 13:45 [PATCH] Revert "ASoC: core: mark SND_SOC_BYTES_EXT as deprecated" Takashi Sakamoto
2016-09-15 14:21 ` Charles Keepax
2016-09-15 14:41 ` Takashi Sakamoto
2016-09-15 14:54 ` Mark Brown [this message]
2016-09-15 22:29 ` Takashi Sakamoto
2016-09-15 23:26 ` Takashi Sakamoto
-- strict thread matches above, loose matches on Subject: below --
2016-09-15 23:06 Takashi Sakamoto
2016-09-16 10:52 ` Mark Brown
2016-09-16 13:21 ` Takashi Sakamoto
2016-09-16 14:11 ` 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=20160915145429.GL27974@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=clemens@ladisch.de \
--cc=o-takashi@sakamocchi.jp \
--cc=tiwai@suse.de \
--cc=vinod.koul@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;
as well as URLs for NNTP newsgroup(s).