linux-kernel - Re: 转发: [PATCH] usb: serial: update CH34x driver in drivers/usb/serial

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

Date:   Tue, 20 Sep 2016 21:38:10 +0200
From:   Grigori Goronzy <greg@...wn.ath.cx>
To:     Aidan Thornton <makosoft@...il.com>
Cc:     Greg KH <gregkh@...uxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-usb@...r.kernel.org, m.othacehe@...il.com,
        david.ward@...mit.edu, johan@...nel.org, pberger@...mson.com,
        WCH Tech Group <tech@...chiphead.com>,
        konstantin.shkolnyy@...il.com, Eddi De Pieri <eddi@...ieri.net>
Subject: Re: 转发: [PATCH] usb: serial: update CH34x driver in drivers/usb/serial

On 2016-09-15 01:03, Aidan Thornton wrote:
>> 
>> thanks,
>> 
>> greg k-h
> 
> It looks like someone by the name of Grigori Goronzy (CCed) had a
> patch series or four attempting to do this that just never went
> anywhere like all the other attempts. Might be worth someone talking
> to him or looking at his patches. Seriously, this is... I was
> considering trying to get parity support merged so I don't have to
> keep patching it in, but it feels like a total waste of effort at this
> point after seeing all the other attempts.

Hi everyone,

sorry for not following up on the patches.  There were some odd 
compatibility issues reported by one user and then I got busy with other 
things, so this got sidetracked.  But just a few days ago the lack of 
working parity annoyed me again. STM32 bootloaders need parity.  I'll 
take a look at your revised patches, Aidan.  Maybe we can finally get 
this done.

About the compatibility issues, I never managed to reproduce them and I 
concluded in the end that it might be something unrelated.

The person that reported compatibility issues with the patch series was 
Eddi De Pieri <eddi@...ieri.net>.

Best regards
Grigori