From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on archive.lwn.net X-Spam-Level: X-Spam-Status: No, score=-5.9 required=5.0 tests=DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by archive.lwn.net (Postfix) with ESMTP id 6FFEB7E3DF for ; Wed, 8 Aug 2018 16:44:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727165AbeHHTFK (ORCPT ); Wed, 8 Aug 2018 15:05:10 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:58764 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727069AbeHHTFK (ORCPT ); Wed, 8 Aug 2018 15:05:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=ZMAGAR5lfWa8Gmxy2bmMcvRwUzxvBj23x03HN3qcDPM=; b=GvfBL0Ex7V+sKbiGf4ZT87j5qeSZEqyCrROguRMSBL4uhrt0E/AtfG9ugdc9v/sZNSFEVAOO/OXCGtH8B6al0eEeO2cLu5ix/Nxnqw6APRLMl7Ms/dnDUCwH5oTuw9du2yQczzyCdfuDu2oMDFnU+49HDfLg0pG/JyhLekfiQYo=; Received: from andrew by vps0.lunn.ch with local (Exim 4.84_2) (envelope-from ) id 1fnRZ4-0007YV-AU; Wed, 08 Aug 2018 18:44:02 +0200 Date: Wed, 8 Aug 2018 18:44:02 +0200 From: Andrew Lunn To: Bartosz Golaszewski Cc: Wolfram Sang , Bartosz Golaszewski , Jonathan Corbet , Sekhar Nori , Kevin Hilman , Russell King , Arnd Bergmann , Greg Kroah-Hartman , David Woodhouse , Brian Norris , Boris Brezillon , Marek Vasut , Richard Weinberger , Grygorii Strashko , "David S . Miller" , Srinivas Kandagatla , Naren , Mauro Carvalho Chehab , Andrew Morton , Lukas Wunner , Dan Carpenter , Florian Fainelli , Ivan Khoronzhuk , Sven Van Asbroeck , Paolo Abeni , Alban Bedel , Rob Herring , David Lechner , linux-doc , LKML , arm-soc , linux-i2c , linux-mtd@lists.infradead.org, Linux-OMAP , netdev@vger.kernel.org Subject: Re: [PATCH 00/28] at24: remove at24_platform_data Message-ID: <20180808164402.GH7275@lunn.ch> References: <20180808153150.23444-1-brgl@bgdev.pl> <20180808155548.s7p4xqsjywz3psrj@ninjato> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On Wed, Aug 08, 2018 at 06:27:25PM +0200, Bartosz Golaszewski wrote: > 2018-08-08 17:55 GMT+02:00 Wolfram Sang : > > On Wed, Aug 08, 2018 at 05:31:22PM +0200, Bartosz Golaszewski wrote: > >> From: Bartosz Golaszewski > >> > >> This is a follow-up to the previously rejected series[1] which partially > >> removed the at24_platform_data structure. After further development and > >> taking reviews into account, this series finally removes that struct > >> completely but not without touching many different parts of the code > >> base. > >> > >> Since I took over maintainership of the at24 driver I've been working > >> towards removing at24_platform_data in favor for device properties. > > > > Wooha, nice work. I can't really comment on it but wondered how you want > > to upstream it (after reviews)? Pull request of an immutable branch for > > nvmem-tree sounds best to me. Then I could also pull it in if i2c needs > > it. Probably same situation for arm-soc... > > > > I initially wanted to merge small parts of it starting with v4.18, but > there were some voices against merging APIs without users. I'm not > sure how it should go in. There'll be a need for multiple immutable > branches most probably... Hi Bartosz What this series does is show all the different parts are now available, and can be reviewed as a whole. Once that review is completed, merging in parts then becomes possible. It looks like you could probably merge the nvmem, mtd and net parts independently via there maintainers for 4.20, since i don't think there are any dependencies. The arm-soc changes in 4.21, and the removal of the platform data in 4.22? Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: [PATCH 00/28] at24: remove at24_platform_data Date: Wed, 8 Aug 2018 18:44:02 +0200 Message-ID: <20180808164402.GH7275@lunn.ch> References: <20180808153150.23444-1-brgl@bgdev.pl> <20180808155548.s7p4xqsjywz3psrj@ninjato> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Bartosz Golaszewski Cc: Wolfram Sang , Sekhar Nori , Srinivas Kandagatla , linux-i2c , Mauro Carvalho Chehab , Rob Herring , Florian Fainelli , Kevin Hilman , Richard Weinberger , Bartosz Golaszewski , linux-doc , Russell King , Marek Vasut , Paolo Abeni , Dan Carpenter , Grygorii Strashko , David Lechner , Arnd Bergmann , Sven Van Asbroeck , Boris Brezillon , linux-mtd@lists.infradead.org, Linux-OMAP , arm-soc List-Id: linux-i2c@vger.kernel.org On Wed, Aug 08, 2018 at 06:27:25PM +0200, Bartosz Golaszewski wrote: > 2018-08-08 17:55 GMT+02:00 Wolfram Sang : > > On Wed, Aug 08, 2018 at 05:31:22PM +0200, Bartosz Golaszewski wrote: > >> From: Bartosz Golaszewski > >> > >> This is a follow-up to the previously rejected series[1] which partially > >> removed the at24_platform_data structure. After further development and > >> taking reviews into account, this series finally removes that struct > >> completely but not without touching many different parts of the code > >> base. > >> > >> Since I took over maintainership of the at24 driver I've been working > >> towards removing at24_platform_data in favor for device properties. > > > > Wooha, nice work. I can't really comment on it but wondered how you want > > to upstream it (after reviews)? Pull request of an immutable branch for > > nvmem-tree sounds best to me. Then I could also pull it in if i2c needs > > it. Probably same situation for arm-soc... > > > > I initially wanted to merge small parts of it starting with v4.18, but > there were some voices against merging APIs without users. I'm not > sure how it should go in. There'll be a need for multiple immutable > branches most probably... Hi Bartosz What this series does is show all the different parts are now available, and can be reviewed as a whole. Once that review is completed, merging in parts then becomes possible. It looks like you could probably merge the nvmem, mtd and net parts independently via there maintainers for 4.20, since i don't think there are any dependencies. The arm-soc changes in 4.21, and the removal of the platform data in 4.22? Andrew From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 8 Aug 2018 18:44:02 +0200 From: Andrew Lunn To: Bartosz Golaszewski Cc: Wolfram Sang , Bartosz Golaszewski , Jonathan Corbet , Sekhar Nori , Kevin Hilman , Russell King , Arnd Bergmann , Greg Kroah-Hartman , David Woodhouse , Brian Norris , Boris Brezillon , Marek Vasut , Richard Weinberger , Grygorii Strashko , "David S . Miller" , Srinivas Kandagatla , Naren , Mauro Carvalho Chehab , Andrew Morton , Lukas Wunner , Dan Carpenter , Florian Fainelli , Ivan Khoronzhuk , Sven Van Asbroeck , Paolo Abeni , Alban Bedel , Rob Herring , David Lechner , linux-doc , LKML , arm-soc , linux-i2c , linux-mtd@lists.infradead.org, Linux-OMAP , netdev@vger.kernel.org Subject: Re: [PATCH 00/28] at24: remove at24_platform_data Message-ID: <20180808164402.GH7275@lunn.ch> References: <20180808153150.23444-1-brgl@bgdev.pl> <20180808155548.s7p4xqsjywz3psrj@ninjato> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, Aug 08, 2018 at 06:27:25PM +0200, Bartosz Golaszewski wrote: > 2018-08-08 17:55 GMT+02:00 Wolfram Sang : > > On Wed, Aug 08, 2018 at 05:31:22PM +0200, Bartosz Golaszewski wrote: > >> From: Bartosz Golaszewski > >> > >> This is a follow-up to the previously rejected series[1] which partially > >> removed the at24_platform_data structure. After further development and > >> taking reviews into account, this series finally removes that struct > >> completely but not without touching many different parts of the code > >> base. > >> > >> Since I took over maintainership of the at24 driver I've been working > >> towards removing at24_platform_data in favor for device properties. > > > > Wooha, nice work. I can't really comment on it but wondered how you want > > to upstream it (after reviews)? Pull request of an immutable branch for > > nvmem-tree sounds best to me. Then I could also pull it in if i2c needs > > it. Probably same situation for arm-soc... > > > > I initially wanted to merge small parts of it starting with v4.18, but > there were some voices against merging APIs without users. I'm not > sure how it should go in. There'll be a need for multiple immutable > branches most probably... Hi Bartosz What this series does is show all the different parts are now available, and can be reviewed as a whole. Once that review is completed, merging in parts then becomes possible. It looks like you could probably merge the nvmem, mtd and net parts independently via there maintainers for 4.20, since i don't think there are any dependencies. The arm-soc changes in 4.21, and the removal of the platform data in 4.22? Andrew From mboxrd@z Thu Jan 1 00:00:00 1970 From: andrew@lunn.ch (Andrew Lunn) Date: Wed, 8 Aug 2018 18:44:02 +0200 Subject: [PATCH 00/28] at24: remove at24_platform_data In-Reply-To: References: <20180808153150.23444-1-brgl@bgdev.pl> <20180808155548.s7p4xqsjywz3psrj@ninjato> Message-ID: <20180808164402.GH7275@lunn.ch> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, Aug 08, 2018 at 06:27:25PM +0200, Bartosz Golaszewski wrote: > 2018-08-08 17:55 GMT+02:00 Wolfram Sang : > > On Wed, Aug 08, 2018 at 05:31:22PM +0200, Bartosz Golaszewski wrote: > >> From: Bartosz Golaszewski > >> > >> This is a follow-up to the previously rejected series[1] which partially > >> removed the at24_platform_data structure. After further development and > >> taking reviews into account, this series finally removes that struct > >> completely but not without touching many different parts of the code > >> base. > >> > >> Since I took over maintainership of the at24 driver I've been working > >> towards removing at24_platform_data in favor for device properties. > > > > Wooha, nice work. I can't really comment on it but wondered how you want > > to upstream it (after reviews)? Pull request of an immutable branch for > > nvmem-tree sounds best to me. Then I could also pull it in if i2c needs > > it. Probably same situation for arm-soc... > > > > I initially wanted to merge small parts of it starting with v4.18, but > there were some voices against merging APIs without users. I'm not > sure how it should go in. There'll be a need for multiple immutable > branches most probably... Hi Bartosz What this series does is show all the different parts are now available, and can be reviewed as a whole. Once that review is completed, merging in parts then becomes possible. It looks like you could probably merge the nvmem, mtd and net parts independently via there maintainers for 4.20, since i don't think there are any dependencies. The arm-soc changes in 4.21, and the removal of the platform data in 4.22? Andrew From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: [PATCH 00/28] at24: remove at24_platform_data Date: Wed, 8 Aug 2018 18:44:02 +0200 Message-ID: <20180808164402.GH7275@lunn.ch> References: <20180808153150.23444-1-brgl@bgdev.pl> <20180808155548.s7p4xqsjywz3psrj@ninjato> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Wolfram Sang , Sekhar Nori , Srinivas Kandagatla , linux-i2c , Mauro Carvalho Chehab , Rob Herring , Florian Fainelli , Kevin Hilman , Richard Weinberger , Bartosz Golaszewski , linux-doc , Russell King , Marek Vasut , Paolo Abeni , Dan Carpenter , Grygorii Strashko , David Lechner , Arnd Bergmann , Sven Van Asbroeck , Boris Brezillon , linux-mtd@lists.infradead.org, Linux-OMAP , arm-soc Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org List-Id: netdev.vger.kernel.org On Wed, Aug 08, 2018 at 06:27:25PM +0200, Bartosz Golaszewski wrote: > 2018-08-08 17:55 GMT+02:00 Wolfram Sang : > > On Wed, Aug 08, 2018 at 05:31:22PM +0200, Bartosz Golaszewski wrote: > >> From: Bartosz Golaszewski > >> > >> This is a follow-up to the previously rejected series[1] which partially > >> removed the at24_platform_data structure. After further development and > >> taking reviews into account, this series finally removes that struct > >> completely but not without touching many different parts of the code > >> base. > >> > >> Since I took over maintainership of the at24 driver I've been working > >> towards removing at24_platform_data in favor for device properties. > > > > Wooha, nice work. I can't really comment on it but wondered how you want > > to upstream it (after reviews)? Pull request of an immutable branch for > > nvmem-tree sounds best to me. Then I could also pull it in if i2c needs > > it. Probably same situation for arm-soc... > > > > I initially wanted to merge small parts of it starting with v4.18, but > there were some voices against merging APIs without users. I'm not > sure how it should go in. There'll be a need for multiple immutable > branches most probably... Hi Bartosz What this series does is show all the different parts are now available, and can be reviewed as a whole. Once that review is completed, merging in parts then becomes possible. It looks like you could probably merge the nvmem, mtd and net parts independently via there maintainers for 4.20, since i don't think there are any dependencies. The arm-soc changes in 4.21, and the removal of the platform data in 4.22? Andrew