From mboxrd@z Thu Jan 1 00:00:00 1970 From: f.fainelli@gmail.com (Florian Fainelli) Date: Tue, 29 Dec 2015 14:56:24 -0800 Subject: [RESEND PATCH v1 0/4] Add support emac for the RK3036 SoC platform In-Reply-To: <3925713.yDzK1dvrIv@diego> References: <1451287341-16453-1-git-send-email-zhengxing@rock-chips.com> <20151229.155314.1522114236952280828.davem@davemloft.net> <3925713.yDzK1dvrIv@diego> Message-ID: <20898DB3-4FB5-4130-A69D-1DE4BC819A5C@gmail.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On December 29, 2015 2:27:55 PM PST, "Heiko St?bner" wrote: >Hi Dave, > >Am Dienstag, 29. Dezember 2015, 15:53:14 schrieb David Miller: >> You have to submit this series properly, the same problem happend >twice >> now. >> >> When you submit a series you should: >> >> 1) Make it clear which tree you expect these changes to be applied >> to. Here it is completely ambiguous, do you want it to go into >> my networking tree or some other subsystem tree? >> >> 2) You MUST keep all parties informed about all patches for a series >> like this. That means you cannot drop netdev from patch #4 as >> you did both times. Doing this aggravates the situation for >> #1 even more, because if a patch is not CC:'d to netdev it does >> not enter patchwork. And if it doesn't go into patchwork, I'm >> not looking at it. > >I guess that is some unfortunate result of git send-email combined with > >get_maintainer.pl . In general I also prefer to see the whole series, >but have >gotten such partial series from other maintainers as well in the past, >so it >seems to be depending on preferences somewhat. You could run get_maintainer.pl against the individual patches in the series, merge the cc list somewhere in a file/variable and then do the actual mail submission with that full list for all patches. There could be a way to automate that with a bit of help from git send-email eventually. -- Florian