From: Johan Hovold <johan@kernel.org>
To: Mans Rullgard <mans@mansr.com>
Cc: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Karoly Pados <pados@pados.hu>
Subject: USB: serial: cp210x: support all gpios on CP2102N QFN28 package
Date: Fri, 25 Jan 2019 10:52:25 +0100 [thread overview]
Message-ID: <20190125095225.GE3691@localhost> (raw)
On Thu, Jan 24, 2019 at 01:48:39PM +0000, Mans Rullgard wrote:
> The QFN28 package version of the CP2102N has three additional gpio pins.
> Add support for these.
>
> Signed-off-by: Mans Rullgard <mans@mansr.com>
Thanks for investigating and enabling support for the remaining pins.
Now applied.
Johan
WARNING: multiple messages have this Message-ID (diff)
From: Johan Hovold <johan@kernel.org>
To: Mans Rullgard <mans@mansr.com>
Cc: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Karoly Pados <pados@pados.hu>
Subject: Re: [PATCH] USB: serial: cp210x: support all gpios on CP2102N QFN28 package
Date: Fri, 25 Jan 2019 10:52:25 +0100 [thread overview]
Message-ID: <20190125095225.GE3691@localhost> (raw)
In-Reply-To: <20190124134839.13316-1-mans@mansr.com>
On Thu, Jan 24, 2019 at 01:48:39PM +0000, Mans Rullgard wrote:
> The QFN28 package version of the CP2102N has three additional gpio pins.
> Add support for these.
>
> Signed-off-by: Mans Rullgard <mans@mansr.com>
Thanks for investigating and enabling support for the remaining pins.
Now applied.
Johan
next reply other threads:[~2019-01-25 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 9:52 Johan Hovold [this message]
2019-01-25 9:52 ` [PATCH] USB: serial: cp210x: support all gpios on CP2102N QFN28 package Johan Hovold
-- strict thread matches above, loose matches on Subject: below --
2019-01-24 13:48 Måns Rullgård
2019-01-24 13:48 ` [PATCH] " Mans Rullgard
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=20190125095225.GE3691@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mans@mansr.com \
--cc=pados@pados.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.