linux-kernel - Re: [PATCH 0/3] usb: USB Type-C Class and driver for UCSI

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 6 May 2016 07:10:38 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Heikki Krogerus <heikki.krogerus@...ux.intel.com>
Cc:	Felipe Balbi <balbi@...nel.org>,
	Greg KH <gregkh@...uxfoundation.org>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	Mathias Nyman <mathias.nyman@...ux.intel.com>
Subject: Re: [PATCH 0/3] usb: USB Type-C Class and driver for UCSI

Hello Heikki,

On 05/06/2016 01:29 AM, Heikki Krogerus wrote:
> On Fri, May 06, 2016 at 01:05:05AM -0700, Guenter Roeck wrote:
[ ... ]
>> I know there has been a lengthy discussion about the patch set, but I may
>> have missed the conclusion. Is there some reason to _not_ advance it
>> that I may have missed ?
>
> No, we are still continuing with the class driver. We just descided to
> split the UCIS into separate driver for now, just because we needed it
> to be supported fast. But I did mention in the commit message of the
> UCSI patch that the goal is to merge that into a Type-C framework once
> it's awailable.
>
Yes, I noticed. I had suspected that your need for a driver now was the
reason for the stand-alone driver. Felipe's response got me concerned
for a minute, though.

Thanks,
Guenter