From: Grigori Goronzy <greg@chown.ath.cx>
To: Aidan Thornton <makosoft@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org, m.othacehe@gmail.com,
david.ward@ll.mit.edu, johan@kernel.org, pberger@brimson.com,
WCH Tech Group <tech@winchiphead.com>,
konstantin.shkolnyy@gmail.com, Eddi De Pieri <eddi@depieri.net>
Subject: Re: 转发: [PATCH] usb: serial: update CH34x driver in drivers/usb/serial
Date: Tue, 20 Sep 2016 21:38:10 +0200 [thread overview]
Message-ID: <5436a97dcafdc8601612c1f5811408c3@chown.ath.cx> (raw)
In-Reply-To: <CAB=c7Tr8FhXNJyMgviLbmNcWQKNWhum_16zRnym0tyP_f9v94w@mail.gmail.com>
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@depieri.net>.
Best regards
Grigori
prev parent reply other threads:[~2016-09-20 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <002401d1cddb$2f70ab60$8e520220$@com>
2016-06-24 15:09 ` Greg KH
[not found] ` <CAB=c7Tr8FhXNJyMgviLbmNcWQKNWhum_16zRnym0tyP_f9v94w@mail.gmail.com>
2016-09-15 5:56 ` Greg KH
2016-09-15 10:19 ` Aidan Thornton
2016-09-15 11:00 ` Johan Hovold
2016-09-20 19:38 ` Grigori Goronzy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5436a97dcafdc8601612c1f5811408c3@chown.ath.cx \
--to=greg@chown.ath.cx \
--cc=david.ward@ll.mit.edu \
--cc=eddi@depieri.net \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=konstantin.shkolnyy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.othacehe@gmail.com \
--cc=makosoft@gmail.com \
--cc=pberger@brimson.com \
--cc=tech@winchiphead.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®