From: Sergej Bauer <sbauer@blackbox.su>
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Markus.Elfring@web.de,
Bryan Whitehead <bryan.whitehead@microchip.com>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
"David S. Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] lan743x: fix for potential NULL pointer dereference with bare card
Date: Fri, 27 Nov 2020 11:39:41 +0300 [thread overview]
Message-ID: <29226509.5m4h6Y2tBG@metabook> (raw)
In-Reply-To: <CAGngYiXFJTQN3+-HC7L0F5cVfXBpPLS3O4gbaSdMmNurzgnwGw@mail.gmail.com>
Hi Sven.
> Hi Jakub, Sergej,
>
> On Tue, Nov 3, 2020 at 8:41 PM Jakub Kicinski <kuba@kernel.org> wrote:
> > On Mon, 2 Nov 2020 01:35:55 +0300 Sergej Bauer wrote:
> > > This is the 3rd revision of the patch fix for potential null pointer
> > > dereference with lan743x card.
> >
> > Applied, thanks!
>
> I noticed that this went into net-next. Is there a chance that it could also
> be added to net? It's a real issue on 5.9, and the patch applies cleanly
> there.
It's my mistake - I missed pointing of stable branch.
Should I resend the patch (with tag Cc:stable@vger.kernel.org)?
Regards,
Sergej.
next prev parent reply other threads:[~2020-11-27 8:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <220201101203820.GD1109407@lunn.ch>
2020-11-01 22:35 ` [PATCH v3] lan743x: fix for potential NULL pointer dereference with bare card Sergej Bauer
2020-11-04 1:38 ` Jakub Kicinski
2020-11-04 19:46 ` Sergej Bauer
2020-11-26 14:22 ` Sven Van Asbroeck
2020-11-27 8:39 ` Sergej Bauer [this message]
2020-11-27 16:39 ` Jakub Kicinski
2020-12-15 16:12 ` [PATCH v4] " Sergej Bauer
2020-12-15 23:39 ` patchwork-bot+netdevbpf
2020-12-16 1:12 ` Jakub Kicinski
2020-12-16 1:35 ` Sergej Bauer
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=29226509.5m4h6Y2tBG@metabook \
--to=sbauer@blackbox.su \
--cc=Markus.Elfring@web.de \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=thesven73@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