From: Lars Melin <larsm17@gmail.com>
To: Sasha Levin <sashal@kernel.org>,
Kristian Evensen <kristian.evensen@gmail.com>
Cc: linux-kernel@vger.kernel.org, stable <stable@vger.kernel.org>,
"Daniele Palmas" <dnlplm@gmail.com>, "Bjørn Mork" <bjorn@mork.no>,
"Jakub Kicinski" <jakub.kicinski@netronome.com>,
"Network Development" <netdev@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 4.14 17/33] net: usb: qmi_wwan: add Telit 0x1050 composition
Date: Tue, 8 Sep 2020 07:33:21 +0700 [thread overview]
Message-ID: <6e09f3e2-674d-f7c1-e868-c170dff1dbb9@gmail.com> (raw)
In-Reply-To: <20200907181552.GN8670@sasha-vm>
On 9/8/2020 01:15, Sasha Levin wrote:
> On Mon, Sep 07, 2020 at 11:36:37AM +0200, Kristian Evensen wrote:
// snip
>> When testing the FN980 with kernel 4.14, I noticed that the qmi device
>> was not there. Checking the git log, I see that this patch was never
>> applied. The patch applies fine, so I guess it was just missed
>> somewhere. If it could be added to the next 4.14 release, it would be
>> much appreciated.
>
> Interesting, yes - I'm not sure why it's missing. I'll queue it up.
>
The patch is missing from all 4.x LTS kernels, not only 4.14
br
Lars
next prev parent reply other threads:[~2020-09-08 0:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191026132110.4026-1-sashal@kernel.org>
2019-10-26 13:20 ` [PATCH AUTOSEL 4.14 17/33] net: usb: qmi_wwan: add Telit 0x1050 composition Sasha Levin
2020-09-07 9:36 ` Kristian Evensen
2020-09-07 18:15 ` Sasha Levin
2020-09-08 0:33 ` Lars Melin [this message]
2020-09-08 12:12 ` Sasha Levin
2019-10-26 13:21 ` [PATCH AUTOSEL 4.14 25/33] net: usb: sr9800: fix uninitialized local variable Sasha Levin
2019-10-26 13:21 ` [PATCH AUTOSEL 4.14 28/33] usb: hso: obey DMA rules in tiocmget Sasha Levin
2019-10-26 13:21 ` [PATCH AUTOSEL 4.14 30/33] net: usb: lan78xx: Connect PHY before registering MAC Sasha Levin
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=6e09f3e2-674d-f7c1-e868-c170dff1dbb9@gmail.com \
--to=larsm17@gmail.com \
--cc=bjorn@mork.no \
--cc=dnlplm@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=kristian.evensen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sashal@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).