From: Sasha Levin <sashal@kernel.org>
To: Kristian Evensen <kristian.evensen@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 4.14 0/2] USB: serial: option: Backport Quectel EP06/endpoint patches
Date: Mon, 5 Nov 2018 19:33:14 -0500 [thread overview]
Message-ID: <20181106003314.GZ194472@sasha-vm> (raw)
In-Reply-To: <20181101195247.9448-1-kristian.evensen@gmail.com>
On Thu, Nov 01, 2018 at 08:52:45PM +0100, Kristian Evensen wrote:
>This patch series contains backports for 4.14 of two patches that were
>submitted to stable, but failed to apply. One patch adds support for
>dynamic interface configuration on the Quectel EP06, while the other
>contains an upstream change triggered by the EP06-change.
>
>The reason the patches failed to apply, is that option_probe() in option.c
>has been changed upstream. A slight reshuffling of the changes in "USB:
>serial: option: improve Quectel EP06 detection" was required. "USB: serial:
>option: add two-endpoints device-id flag" applied cleanly after the change,
>but a small change was still needed. The upstream commit removes a variable
>that is still in use in 4.14, so this change is removed.
>
>Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
>
>Johan Hovold (1):
> USB: serial: option: add two-endpoints device-id flag
>
>Kristian Evensen (1):
> USB: serial: option: improve Quectel EP06 detection
>
> drivers/usb/serial/option.c | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
Queued both for 4.14, thank you.
--
Thanks,
Sasha
prev parent reply other threads:[~2018-11-06 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 19:52 [PATCH 4.14 0/2] USB: serial: option: Backport Quectel EP06/endpoint patches Kristian Evensen
2018-11-01 19:52 ` [PATCH 4.14 1/2] USB: serial: option: improve Quectel EP06 detection Kristian Evensen
2018-11-01 19:52 ` [PATCH 4.14 2/2] USB: serial: option: add two-endpoints device-id flag Kristian Evensen
2018-11-06 0:33 ` Sasha Levin [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=20181106003314.GZ194472@sasha-vm \
--to=sashal@kernel.org \
--cc=kristian.evensen@gmail.com \
--cc=stable@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