Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754522AbbL3KSF (ORCPT ); Wed, 30 Dec 2015 05:18:05 -0500 Received: from mail-ig0-f170.google.com ([209.85.213.170]:38301 "EHLO mail-ig0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752857AbbL3KSA convert rfc822-to-8bit (ORCPT ); Wed, 30 Dec 2015 05:18:00 -0500 MIME-Version: 1.0 In-Reply-To: <20151229.204847.578920480799799256.davem@davemloft.net> References: <1451287341-16453-1-git-send-email-zhengxing@rock-chips.com> <20151229.155314.1522114236952280828.davem@davemloft.net> <3925713.yDzK1dvrIv@diego> <20151229.204847.578920480799799256.davem@davemloft.net> Date: Wed, 30 Dec 2015 11:17:59 +0100 X-Google-Sender-Auth: 0Tjd70VFc8yKTmg6shU66COJHB0 Message-ID: Subject: Re: [RESEND PATCH v1 0/4] Add support emac for the RK3036 SoC platform From: Geert Uytterhoeven To: David Miller Cc: =?UTF-8?Q?Heiko_St=C3=BCbner?= , zhengxing@rock-chips.com, "open list:ARM/Rockchip SoC..." , Kees Cook , leozwang@google.comi, Russell King , "devicetree@vger.kernel.org" , "netdev@vger.kernel.org" , Paul Gortmaker , Kumar Gala , "linux-kernel@vger.kernel.org" , Ian Campbell , Pawel Moll , Mark Rutland , Rob Herring , "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2489 Lines: 58 Hi David, On Wed, Dec 30, 2015 at 2:48 AM, David Miller wrote: > From: Heiko Stübner > Date: Tue, 29 Dec 2015 23:27:55 +0100 >> 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. >> >> For the series at hand, the 4th patch is the devicetree addition, which the >> expected way is me picking it up, after you are comfortable with the code- >> related changes. > > Why would it not be appropriate for a DT file change to go into my tree > if it corresponds to functionality created by the rest of the patches > in the series? Because the DT change is very likely to conflict with other DT changes. That's why typically all DT changes go in through the platform/architecture maintainer. > It looks better to put it all together as a unit, via one series, with > a merge commit containing your "[PATCH 0/N]" description in the commit > message. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/