From mboxrd@z Thu Jan 1 00:00:00 1970 From: sylvester.nawrocki@gmail.com (Sylwester Nawrocki) Date: Wed, 01 May 2013 12:28:17 +0200 Subject: [alsa-devel] [PATCH] MAINTAINERS: Add linux-samsung-soc list to all related entries In-Reply-To: <20130430132755.GB1023@sirena.org.uk> References: <1366572050-626-1-git-send-email-tomasz.figa@gmail.com> <20130430132755.GB1023@sirena.org.uk> Message-ID: <5180EE41.50302@gmail.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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.