public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Zago <frank@zago.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
	Jan-Niklas Burfeind <kernel@aiyionpri.me>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Wolfram Sang <wsa@kernel.org>, Johan Hovold <johan@kernel.org>,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH 1/2] Revert "USB: serial: ch341: add new Product ID for CH341A"
Date: Tue, 20 Apr 2021 10:27:39 -0500	[thread overview]
Message-ID: <0c2922e1-cc93-32a2-89c2-169ef642ef37@zago.net> (raw)
In-Reply-To: <YH6Gv9QG5VusXlgy@kroah.com>

On 4/20/21 2:46 AM, Greg Kroah-Hartman wrote:
> On Mon, Apr 19, 2021 at 09:25:19PM -0500, Frank Zago wrote:
>> From: frank zago <frank@zago.net>
>>
>> The 0x5512 USB PID is for the I2C/GPIO/SPI interfaces. UART is still
>> present but only the TX and RX pins are available; DTS, DTR, ... are
>> used for other things. Remove the PID, and let a I2C driver bind to
>> it.
>>
>> Existing CH341 boards usually have physical jumpers to switch between
>> the 3 modes.
>>
>> This reverts commit 46ee4abb10a07bd8f8ce910ee6b4ae6a947d7f63.
>>
>> Signed-off-by: Frank Zago <frank@zago.net>
>> Signed-off-by: frank zago <frank@zago.net>
> 
> Why are you signing off twice?
> 

I did it in the patch, then git send-mail added another one. That'll be fixed in the next revision.

Regards,
Frank

      reply	other threads:[~2021-04-20 15:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20  2:25 [PATCH 1/2] Revert "USB: serial: ch341: add new Product ID for CH341A" Frank Zago
2021-04-20  2:25 ` [PATCH 2/2] USB: misc: Add driver for the WCH CH341 in I2C/GPIO mode Frank Zago
2021-04-20  2:32   ` Randy Dunlap
2021-04-20  7:46 ` [PATCH 1/2] Revert "USB: serial: ch341: add new Product ID for CH341A" Greg Kroah-Hartman
2021-04-20 15:27   ` Frank Zago [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=0c2922e1-cc93-32a2-89c2-169ef642ef37@zago.net \
    --to=frank@zago.net \
    --cc=bgolaszewski@baylibre.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=kernel@aiyionpri.me \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=wsa@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