From: John Hsu <KCHSU0@nuvoton.com>
To: Mark Brown <broonie@kernel.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Anatol Pomozov <anatol.pomozov@gmail.com>,
Ben Zhang <benzh@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
YHCHuang@nuvoton.com, CTLIN0@nuvoton.com,
Yong Zhi <yong.zhi@intel.com>
Subject: Re: [PATCH] ASoC: Extend FLL function
Date: Sat, 27 Feb 2016 00:16:59 +0800 [thread overview]
Message-ID: <56D07A7B.7000104@nuvoton.com> (raw)
In-Reply-To: <20160226013403.GB18327@sirena.org.uk>
Hi
On 2/26/2016 9:34 AM, Mark Brown wrote:
> On Fri, Feb 26, 2016 at 01:34:19AM +0800, John Hsu wrote:
>
>> On 2/25/2016 9:55 AM, Mark Brown wrote:
>>
>
>
>>> I don't have whatever this patch is (I suspect the fact that there were
>>> concerns raised meant I expected a new version). Please do try to use
>>> subject lines reflecting the style to the subsystem.
>>>
>
>
>> Do you mean I need to resubmit this patch and in-reply-to Message-ID of this
>> mail?
>>
>
> Yes, you need to resubmit the patch. No, you do not need to do it in
> reply to this e-mail.
>
>
I'll submit it again with proper subject.
>> I don't really catch the meaning of "use subject lines reflecting the style
>> to the subsystem".
>> Could you tell me more detail about it? Thank you very much.
>>
>
> If you look at all the other driver commits you'll see that their
> subject lines start "ASoC: driver: " .
>
Yes, I get it. I forgot to do that. Thanks for your remind.
next prev parent reply other threads:[~2016-02-26 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 7:55 [PATCH] ASoC: Extend FLL function John Hsu
2015-12-31 9:14 ` Anatol Pomozov
2016-01-04 10:04 ` John Hsu
2016-02-24 22:51 ` John Hsu
2016-02-25 1:55 ` Mark Brown
2016-02-25 17:34 ` John Hsu
2016-02-26 1:34 ` Mark Brown
2016-02-26 16:16 ` John Hsu [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-06 7:27 [PATCH] ASoC: extend " John Hsu
2016-01-07 1:26 ` Anatol Pomozov
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=56D07A7B.7000104@nuvoton.com \
--to=kchsu0@nuvoton.com \
--cc=CTLIN0@nuvoton.com \
--cc=YHCHuang@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=anatol.pomozov@gmail.com \
--cc=benzh@chromium.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=yong.zhi@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