lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 29 Dec 2015 14:56:24 -0800 From: Florian Fainelli <f.fainelli@...il.com> To: Heiko Stübner <heiko@...ech.de>, David Miller <davem@...emloft.net> CC: zhengxing@...k-chips.com, linux-rockchip@...ts.infradead.org, keescook@...gle.com, leozwang@...gle.comi, linux@....linux.org.uk, devicetree@...r.kernel.org, netdev@...r.kernel.org, paul.gortmaker@...driver.com, galak@...eaurora.org, linux-kernel@...r.kernel.org, ijc+devicetree@...lion.org.uk, pawel.moll@....com, geert@...ux-m68k.org, mark.rutland@....com, robh+dt@...nel.org, linux-arm-kernel@...ts.infradead.org Subject: Re: [RESEND PATCH v1 0/4] Add support emac for the RK3036 SoC platform On December 29, 2015 2:27:55 PM PST, "Heiko Stübner" <heiko@...ech.de> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists