linux-kernel - Re: typec: tcpm/tcpci drivers acceptable for drivers/staging in v4.12 ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20170425182509.GA10594@roeck-us.net>
Date:   Tue, 25 Apr 2017 11:25:09 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org,
        Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
        badhri@...gle.com, Oliver Neukum <oneukum@...e.com>,
        Mats Karrman <mats.dev.list@...il.com>,
        Felipe Balbi <felipe.balbi@...ux.intel.com>,
        linux-usb@...r.kernel.org
Subject: Re: typec: tcpm/tcpci drivers acceptable for drivers/staging in
 v4.12 ?

On Tue, Apr 25, 2017 at 08:02:54PM +0200, Greg Kroah-Hartman wrote:
> On Tue, Apr 25, 2017 at 10:54:02AM -0700, Guenter Roeck wrote:
> > On Tue, Apr 25, 2017 at 07:37:42PM +0200, Greg Kroah-Hartman wrote:
> > > On Tue, Apr 25, 2017 at 09:50:31AM -0700, Guenter Roeck wrote:
> > > > Hi Greg,
> > > > 
> > > > would you be open to accepting the tcpm [1] and tcpci [2] drivers into
> > > > drivers/staging for v4.12 ?
> > > 
> > > What's the rush?
> > > 
> > 
> > It has been a long time, and it avoids duplicate work and submissions,
> > including for drivers depending on it, such as the fusb302 driver submitted
> > by Hans de Goede [1] for which we have a (not yet published) driver based on
> > tcpm as well. If for nothing else, it widens the audience.
> 
> Ok, fair enough, send away!
> 
> And getting a sane fusb302 driver would be great.  The ones I have seen
> are just so bad...
> 

It should hopefully be less insane :-). Looking forward to get your feedback.
We are still trying to figure out if there is anything we have to watch out
for before we can make it available; it is currently sitting in a private
Android branch and we don't want to get into trouble. Most likely we are just
over-cautious. Should hopefully be a matter of days.

Thanks,
Guenter