From: Joe Perches <joe@perches.com>
To: Leif Neland <leif@neland.dk>,
linux-kernel@vger.kernel.org, Johan Hovold <johan@kernel.org>
Cc: linux-usb <linux-usb@vger.kernel.org>
Subject: Re: Patch for drivers/usb/serial/ch341.c enabling parity
Date: Sun, 02 Apr 2017 10:12:38 -0700 [thread overview]
Message-ID: <1491153158.27353.42.camel@perches.com> (raw)
In-Reply-To: <CAJ=8bT4dO=WQsm2C-vkcFWe9GNx9ht8D28kRnJvdx6zS9w7=nw@mail.gmail.com>
On Sun, 2017-04-02 at 18:57 +0200, Leif Neland wrote:
> There is a patch
> https://github.com/karlp/ch341-linux/blob/master/0001-usb-serial-ch341-Add-parity-support.patch
> which enables parity selection for the ch341 USB-RS485 adapter.
>
> From: Karl Palsson <karlp@tweak.net.au> Date: Tue, 18 Mar 2014 23:33:27
> +0000
>
> This adapter is available for cheap on eBay.
>
> The patch made me able to use this adapter for polling my modbus
> power-meter with raspberry pi.
>
> Would it be possible to get this into the official distribution?
>
> Leif Neland
You should really ask the usb serial maintainer.
There's a tool, scripts/get_maintainer.pl, that can
tell you who you ask about who is responsible for
various bits of the kernel.
$ ./scripts/get_maintainer.pl -f drivers/usb/serial/ch341.c
Johan Hovold <johan@kernel.org> (maintainer:USB SERIAL SUBSYSTEM)
Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:USB SUBSYSTEM)
linux-usb@vger.kernel.org (open list:USB SERIAL SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)
next parent reply other threads:[~2017-04-02 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJ=8bT4dO=WQsm2C-vkcFWe9GNx9ht8D28kRnJvdx6zS9w7=nw@mail.gmail.com>
2017-04-02 17:12 ` Joe Perches [this message]
2017-04-03 8:14 ` Patch for drivers/usb/serial/ch341.c enabling parity Johan Hovold
2017-04-02 18:00 Leif Neland
2017-04-03 0:14 ` Fabio Estevam
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=1491153158.27353.42.camel@perches.com \
--to=joe@perches.com \
--cc=johan@kernel.org \
--cc=leif@neland.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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