linux-kernel - Re: [RESEND PATCH v1 0/4] Add support emac for the RK3036 SoC platform

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20151229.155314.1522114236952280828.davem@davemloft.net>
Date:	Tue, 29 Dec 2015 15:53:14 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	zhengxing@...k-chips.com
Cc:	linux-rockchip@...ts.infradead.org, keescook@...gle.com,
	leozwang@...gle.comi, heiko@...ech.de, 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

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.

Thanks.

--
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/