[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160607082527.GB19620@kuha.fi.intel.com>
Date: Tue, 7 Jun 2016 11:25:27 +0300
From: Heikki Krogerus <heikki.krogerus@...ux.intel.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Pavel Machek <pavel@....cz>, Guenter Roeck <linux@...ck-us.net>,
Mathias Nyman <mathias.nyman@...ux.intel.com>,
Felipe Balbi <felipe.balbi@...ux.intel.com>,
Oliver Neukum <oneukum@...e.com>,
Rajaram R <rajaram.officemail@...il.com>,
Andy Shevchenko <andy.shevchenko@...il.com>,
linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: [RFC PATCHv2] usb: USB Type-C Connector Class
On Mon, Jun 06, 2016 at 07:41:28AM -0700, Greg KH wrote:
> On Mon, Jun 06, 2016 at 04:45:09PM +0300, Heikki Krogerus wrote:
> > > For consistency, should this be either type-c/type-c.c or
> > > typec/typec.c?
> >
> > For some reason I like to have the dash in the folder name, but I
> > don't like the idea that the port driver would be in form
> > type-c_something. I would prefer them to be named typec_something. Or
> > maybe just "something" and also name the typec.c maybe class.c or
> > core.c.
> >
> > Is this a big problem? I guess we could just name the folder "typec".
> > Guenter, whats your opinion?
>
> "typec" please.
OK, typec it is.
Thanks,
--
heikki
Powered by blists - more mailing lists