From: jeffy <jeffy.chen@rock-chips.com>
To: Brian Norris <briannorris@chromium.org>
Cc: linux-kernel@vger.kernel.org, dianders@chromium.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: hdmi-codec: Use different name for playback streams
Date: Sat, 12 Aug 2017 08:52:03 +0800 [thread overview]
Message-ID: <598E5133.5050909@rock-chips.com> (raw)
In-Reply-To: <20170811165908.GA67191@google.com>
Hi Brian,
Thanks for noting.
On 08/12/2017 12:59 AM, Brian Norris wrote:
> Hi Jeffy,
>
> You need to be more careful about the addressee's of your patches. No
> one on To/CC is a maintainer or a sufficiently-targeted mailing list. I
> doubt any of the maintainers will read your patch. (I've added
> alsa-devel for you, but given my understanding of at least Mark's
> patchwork workflow -- and of general patch etiquette -- it's important
> the patch is actually sent there in the first place.)
>
> Probably worth resending.
Ok, will do that.
I was using patman to send it, not sure why it didn't work correctly
that time...
prev parent reply other threads:[~2017-08-12 0:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 8:29 [PATCH] ASoC: hdmi-codec: Use different name for playback streams Jeffy Chen
2017-08-11 16:59 ` Brian Norris
2017-08-12 0:52 ` jeffy [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=598E5133.5050909@rock-chips.com \
--to=jeffy.chen@rock-chips.com \
--cc=alsa-devel@alsa-project.org \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=linux-kernel@vger.kernel.org \
/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