From: Arnaud Pouliquen <arnaud.pouliquen@st.com>
To: Mark Brown <broonie@kernel.org>, Eric Anholt <eric@anholt.net>
Cc: Jani Nikula <jani.nikula@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
Jyri Sarha <jsarha@ti.com>
Subject: Re: [PATCH v4 1/3] DRM: add help to get ELD speaker allocation
Date: Thu, 19 Jan 2017 11:49:56 +0100 [thread overview]
Message-ID: <12dd4fb5-978d-f479-208b-1c57ade16e38@st.com> (raw)
In-Reply-To: <20170119102901.h35ynrcztf5z7vb3@sirena.org.uk>
On 01/19/2017 11:29 AM, Mark Brown wrote:
> On Wed, Jan 18, 2017 at 07:38:53AM +1100, Eric Anholt wrote:
>> Mark Brown <broonie@kernel.org> writes:
>
>>> You don't appear to have sent this to any of the DRM
>>> maintainers - it does need review from them.
>
>> It was sent to dri-devel. That's us. And the patch already has
>> a r-b From DRM on it.
>
> I see. For most subsystems you need to actually copy a human to
> make sure that things are seen - just the list isn't enough. In
> terms of it being reviewed one of the problems with DRM not listing
> the reviwers in the MAINTAINERS file or anything is that it's very
> hard for anyone to tell if something is considered a good enough
> review or if it's just a review from someone who happens to
> contribute to DRM sometimes.
>
I limited diffusion to ASoC, as Daniel Vetter and Takashi Iwai
discussed the topic here:
http://www.spinics.net/lists/alsa-devel/msg58114.html
Seems that is was not a good strategy as it leads to discussions..
Sorry for this.
Regards
Arnaud
next prev parent reply other threads:[~2017-01-19 10:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 15:52 [PATCH v4 0/3] Generic HDMI codec: Add channel mapping control Arnaud Pouliquen
2017-01-03 15:52 ` [PATCH v4 1/3] DRM: add help to get ELD speaker allocation Arnaud Pouliquen
2017-01-17 19:19 ` Mark Brown
2017-01-17 20:38 ` Eric Anholt
2017-01-19 10:29 ` Mark Brown
2017-01-19 10:49 ` Arnaud Pouliquen [this message]
2017-01-19 11:18 ` Mark Brown
2017-01-23 7:49 ` Daniel Vetter
2017-01-23 11:41 ` Mark Brown
2017-01-03 15:52 ` [PATCH v4 2/3] ASoC: core: add optional pcm_new callback for DAI driver Arnaud Pouliquen
2017-01-03 15:52 ` [PATCH v4 3/3] ASoC: hdmi-codec: add channel mapping control Arnaud Pouliquen
2017-01-20 15:29 ` Applied "ASoC: hdmi-codec: add channel mapping control" to the asoc tree Mark Brown
[not found] ` <CA+M3ks4rM9Fyt9ysjtruqzJeJj=cBgKddE+n0UFHpP1RMy6OgA@mail.gmail.com>
2017-01-16 8:54 ` [PATCH v4 0/3] Generic HDMI codec: Add channel mapping control Arnaud Pouliquen
2017-01-17 19:39 ` 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=12dd4fb5-978d-f479-208b-1c57ade16e38@st.com \
--to=arnaud.pouliquen@st.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=jani.nikula@intel.com \
--cc=jsarha@ti.com \
--cc=lgirdwood@gmail.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).