From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Brezillon Subject: Re: [PATCH v2 00/25] at24: remove Date: Mon, 19 Nov 2018 10:08:25 +0100 Message-ID: <20181119100825.277b1f97@bbrezillon> References: <20181113140133.17385-1-brgl@bgdev.pl> <20181118170329.788778a8@bbrezillon> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: Sender: netdev-owner@vger.kernel.org To: Bartosz Golaszewski Cc: Sekhar Nori , Kevin Hilman , Russell King , Arnd Bergmann , Greg Kroah-Hartman , David Woodhouse , Brian Norris , Marek Vasut , Richard Weinberger , Nicolas Ferre , "David S . Miller" , Grygorii Strashko , Srinivas Kandagatla , Andrew Lunn , Florian Fainelli , Rob Herring , Frank Rowand , Wolfram Sang , devicetree , netdev List-Id: linux-omap@vger.kernel.org On Mon, 19 Nov 2018 09:58:46 +0100 Bartosz Golaszewski wrote: > niedz., 18 lis 2018 o 17:03 Boris Brezillon > napisaƂ(a): > > > > On Tue, 13 Nov 2018 15:01:08 +0100 > > Bartosz Golaszewski wrote: > > > > > As far as merging of this series goes: I'd like to avoid dragging it over > > > four releases. The series is logically split into five groups: > > > > > > patches 1-2: nvmem and mtd changes > > > patches 3-9: davinci arch-specific changes > > > patches 10-13: networking changes > > > patches 14-24: davinci specific again > > > patch 25: final at24 change > > > > > > With that I believe we can do the following: Greg KH could pick up the > > > first two patches into his char-misc tree. > > > > The char-misc tree? Why not the MTD or NVMEM tree? > > > > There is no NVMEM tree - Srinivas sends his patches to Greg to be > applied to char-misc. Okay, I didn't know that. > > The second patch depends on the first one so in order to avoid more > merging problems I suggested that the MTD patch go through char-misc > as well. If you see a better solution, please let me know. No that's fine, as long as I have an immutable tag/branch I can pull if needed.