Re: [PATCH 3/8] mfd: twl-core: Rename TWL4030_CORE Kconfig option to TWL_CORE

2016-04-07 Thread Lee Jones
On Tue, 29 Mar 2016, Paul Kocialkowski wrote: > Since the twl-core mfd driver is not limited to twl4030 support, but also > supports other chips of the TWL family, it makes sense to rename its matching > Kconfig opton to a non-model-specific name. No, it doesn't. The naming convention is; unless

Re: [PATCH 3/8] mfd: twl-core: Rename TWL4030_CORE Kconfig option to TWL_CORE

2016-04-05 Thread Grygorii Strashko
On 04/02/2016 11:12 PM, Paul Kocialkowski wrote: > Le mercredi 30 mars 2016 à 18:34 +0300, Grygorii Strashko a écrit : >> On 03/29/2016 10:22 PM, Paul Kocialkowski wrote: >>> >>> Since the twl-core mfd driver is not limited to twl4030 support, but also >>> supports other chips of the TWL family, it

Re: [PATCH 3/8] mfd: twl-core: Rename TWL4030_CORE Kconfig option to TWL_CORE

2016-04-02 Thread Paul Kocialkowski
Le mercredi 30 mars 2016 à 18:34 +0300, Grygorii Strashko a écrit : > On 03/29/2016 10:22 PM, Paul Kocialkowski wrote: > > > > Since the twl-core mfd driver is not limited to twl4030 support, but also > > supports other chips of the TWL family, it makes sense to rename its > > matching > > Kconfig

Re: [PATCH 3/8] mfd: twl-core: Rename TWL4030_CORE Kconfig option to TWL_CORE

2016-03-30 Thread Grygorii Strashko
On 03/29/2016 10:22 PM, Paul Kocialkowski wrote: > Since the twl-core mfd driver is not limited to twl4030 support, but also > supports other chips of the TWL family, it makes sense to rename its matching > Kconfig opton to a non-model-specific name. Personally I don't see too much reason for this