From: sylvester.nawrocki@gmail.com (Sylwester Nawrocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH] MAINTAINERS: Add linux-samsung-soc list to all related entries
Date: Wed, 01 May 2013 12:28:17 +0200 [thread overview]
Message-ID: <5180EE41.50302@gmail.com> (raw)
In-Reply-To: <20130430132755.GB1023@sirena.org.uk>
On 04/30/2013 03:27 PM, Mark Brown wrote:
> On Mon, Apr 22, 2013 at 03:23:29PM +0900, Kyungmin Park wrote:
>
>> I don't think it's not required, each tree has each own mailing list. don't
>> need to post all patches to samsung-soc list.
>
> It can be useful to get system level input on some stuff, I guess it
> mostly depends if the people on the generic list mind the extra traffic
> or if they find it useful.
I think this could also improve testing coverage, if more people are aware
of stuff going in through various mailing lists.
Also on a specific subsystem mailing lists yet another SoC specific patches
may not get enough attention, as people care most about the core subsystem
changes.
So I would in general encourage others to Cc linux-samsung-soc, even if the
$subject patch gets ignored.
I seriously doubt anyone would have ever been disturbed with additional
traffic on the list, with its current average of about 20..50 emails per
day.
prev parent reply other threads:[~2013-05-01 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 19:20 [PATCH] MAINTAINERS: Add linux-samsung-soc list to all related entries Tomasz Figa
[not found] ` <CAH9JG2U7Qdq_xQbuqHu6PXzURS2fWwBC=HJmyrXT5n3n_pAa0w@mail.gmail.com>
2013-04-30 13:27 ` [alsa-devel] " Mark Brown
2013-05-01 10:28 ` Sylwester Nawrocki [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=5180EE41.50302@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).