From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751225AbdAMSpP (ORCPT ); Fri, 13 Jan 2017 13:45:15 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:34536 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750914AbdAMSpK (ORCPT ); Fri, 13 Jan 2017 13:45:10 -0500 Date: Fri, 13 Jan 2017 10:22:42 -0800 From: Darren Hart To: Andy Shevchenko Cc: Florian Fainelli , Platform Driver , cphealy@gmail.com, Guenter Roeck , open list Subject: Re: [PATCH] platform/x86: Add IMS/ZII SCU driver Message-ID: <20170113182242.GA17467@localhost.localdomain> References: <20170111212644.9217-1-f.fainelli@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 13, 2017 at 06:38:28PM +0200, Andy Shevchenko wrote: > On Wed, Jan 11, 2017 at 11:26 PM, Florian Fainelli wrote: > > From: Guenter Roeck > > > > This patch adds support for the IMS (now Zodiac Inflight Innovations) > > SCU Generation 1/2/3 platform driver. This driver registers all the > > on-module peripherals: Ethernet switches (Broadcom or Marvell), I2C to > > GPIO expanders, Kontrom CPLD/I2C master, and more. > > > > Signed-off-by: Guenter Roeck > > Signed-off-by: Florian Fainelli > > > --- > > Darren, > > > > This is against your "for-next" branch thanks! > > I'm going to review this later, though few of comments. > > > +config SCU > > No, no. We have enough mess with Intel's SCU/PMIC here, not add more. > > At least add manufacturer as prefix to option and file name. > > Btw, Darren, would it be good idea to start creating folders to make a > bit of order in the subsystem? For first I would move Intel's PMIC/SCU > stuff to somewhere (not sure if it should be per manufacturer or per > function). If we create folder, I'd recommend by manufacturer as that is typically along the lines that our contributors work. Someone with a Dell laptop tends to focus on Dell. The Intel engineers will focus primarily on Intel SoCs, etc. I'd like to avoid getting too granualar as it adds overhead with Makefiles, file navigation, etc. Any thoughts on a minimum file count to justify a new directory? Maybe 5? -- Darren Hart Intel Open Source Technology Center