From: Jakub Kicinski <kuba@kernel.org>
To: Shane Parslow <shaneparslow808@gmail.com>
Cc: M Chetan Kumar <m.chetan.kumar@intel.com>,
Intel Corporation <linuxwwan@intel.com>,
Loic Poulain <loic.poulain@linaro.org>,
Sergey Ryazanov <ryazanov.s.a@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: wwan: iosm: Fix 7360 WWAN card control channel mapping
Date: Mon, 26 Sep 2022 14:37:11 -0700 [thread overview]
Message-ID: <20220926143711.39ba78e9@kernel.org> (raw)
In-Reply-To: <CALi=oTY7Me6g1=jtnZig-MzS-TPOOMQ53ih-78QuF-K+Rs0rUw@mail.gmail.com>
On Mon, 26 Sep 2022 13:51:23 -0700 Shane Parslow wrote:
> There isn't currently an open bug report for this. I can open one if that
> is preferred.
> The gist is that previously, any writes to the 2nd userspace AT port
> would crash the modem.
> This is my first patch -- I apologize if I did things out of order.
The Fixes tag just points us to the commit which introduced the bug,
look thru the git history of the kernel for examples. The expected
format is:
fixes = Fixes: %h (\"%s\")
You need to find the oldest commit where problem exists. This helps
stable tree maintainers to backport the necessary fixes (and netdev
maintainers to make sure that the right tree is targeted).
next prev parent reply other threads:[~2022-09-26 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 4:05 [PATCH net] net: wwan: iosm: Fix 7360 WWAN card control channel mapping Shane Parslow
2022-09-26 20:11 ` Jakub Kicinski
2022-09-26 20:51 ` Shane Parslow
2022-09-26 21:37 ` Jakub Kicinski [this message]
2022-09-26 22:21 ` Shane Parslow
2022-09-27 13:59 ` Jakub Kicinski
2022-09-27 13:43 ` Kumar, M Chetan
2022-09-28 6:06 ` Shane Parslow
2022-10-21 14:04 ` Kumar, M Chetan
2022-10-21 23:54 ` Shane Parslow
2022-10-20 19:13 ` Shane Parslow
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=20220926143711.39ba78e9@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxwwan@intel.com \
--cc=loic.poulain@linaro.org \
--cc=m.chetan.kumar@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ryazanov.s.a@gmail.com \
--cc=shaneparslow808@gmail.com \
/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).