From: Johan Hovold <johan@kernel.org>
To: Charles Yeh <charlesyeh522@gmail.com>
Cc: "Johan Hovold" <johan@kernel.org>,
"Greg KH" <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org,
"Yeh.Charles [葉榮鑫]" <charles-yeh@prolific.com.tw>
Subject: Re: [PATCH] [PATCH v8] USB: serial: pl2303: Add new PID to support PL2303HXN (TYPE_HXN)
Date: Mon, 4 Nov 2019 11:27:13 +0100 [thread overview]
Message-ID: <20191104102713.GG3657@localhost> (raw)
In-Reply-To: <CAAZvQQ5jTcEz8C4QDkRGdS+WiDv7YMMiX4kyLfjUTxxpUSPxwg@mail.gmail.com>
On Mon, Nov 04, 2019 at 06:13:03PM +0800, Charles Yeh wrote:
> > I'm not sure I understand your question; what did you mean here?
> >
> > This patch will be included in Linux 5.5, if that's what your asking.
>
> At 1/18/2018, "USB: serial: pl2303: add new PID to support PL2303TB" is approved
> At 1/27/2018, Greg KH help to update the patch on 4.20, 4.19, 4.14,
> 4.9, 4.4, 3.18 stable tree.
> Therefor, this time can update the patch between 5.5 and 4.4 (or 3.18)?
No, I'm afraid not.
Generally only bug fixes are backported to the stable trees, but we
make an exception for simple patches adding new device ids to existing
drivers.
That's what 4dcf9ddc9ad5 ("USB: serial: pl2303: add new PID to support
PL2303TB") did, and that's why it got backported.
This patch, in contrast, adds support for a new protocol used by a class
of devices which were not supported before, and therefore does not meet
the stable-kernel criteria for backports.
Johan
next prev parent reply other threads:[~2019-11-04 10:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 12:14 [PATCH] [PATCH v8] USB: serial: pl2303: Add new PID to support PL2303HXN (TYPE_HXN) Charles Yeh
2019-10-23 8:56 ` Johan Hovold
2019-11-02 8:58 ` Charles Yeh
2019-11-04 9:15 ` Johan Hovold
2019-11-04 10:13 ` Charles Yeh
2019-11-04 10:27 ` Johan Hovold [this message]
2019-11-04 10:33 ` Charles Yeh
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=20191104102713.GG3657@localhost \
--to=johan@kernel.org \
--cc=charles-yeh@prolific.com.tw \
--cc=charlesyeh522@gmail.com \
--cc=gregkh@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).