From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Lezcano Subject: Re: [PATCH v7 0/5] Reintroduce i.MX EPIT Timer Date: Tue, 10 Jul 2018 17:37:26 +0200 Message-ID: References: <20180611155001.3506-1-peron.clem@gmail.com> <52591c2d-e9df-7078-7cdf-0fd8d06c9ee0@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: =?UTF-8?B?Q2zDqW1lbnQgUMOpcm9u?= Cc: Colin Didier , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Stefan Agner , Thomas Gleixner , Fabio Estevam , Vladimir Zapolskiy , Sascha Hauer , Rob Herring , NXP Linux Team , Pengutronix Kernel Team , =?UTF-8?Q?Cl=c3=a9ment_Peron?= List-Id: devicetree@vger.kernel.org On 10/07/2018 17:22, Clément Péron wrote: > Hi Daniel, > > On Tue, 10 Jul 2018 at 17:12, Daniel Lezcano wrote: >> >> On 10/07/2018 16:55, Clément Péron wrote: >>> Hi, >>> >>> Is there still some remark against merging this ? >> >> How do you want this to be merged ? >> >> Shall I take the two patches related to the timer ? Or Ack them ? > > I'm not an expert on how submitting patches works, it's the first > driver I submit. Ok, so usually this is what happens when there is a set of changes: 1. they all touch the same subsystem (eg. drivers/clocksource), you just send all the patches to the maintainer(s) + mailing list + related people 2. they touch different subsystems: 2.1) the changes are not connected (not related together), you have to split in smaller parts and send the patches to the right subsystem maintainer (so falling back to 1.) 2.2) the changes are connected: 2.2.1) Ask all the different subsystem maintainers to acknowledge the changes and submit the patches to arm-soc@ 2.2.2) Ask each maintainer to take their part if the changes are connected but not interdependent (patches individually won't break the system) You are in the 2.2) situation. My question is do you want 2.2.1) or 2.2.2) ? -- Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog