netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergej Bauer <sbauer@blackbox.su>
To: Jakub Kicinski <kuba@kernel.org>
Cc: patchwork-bot+netdevbpf@kernel.org, andrew@lunn.ch,
	Markus.Elfring@web.de, thesven73@gmail.com,
	bryan.whitehead@microchip.com, UNGLinuxDriver@microchip.com,
	davem@davemloft.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] lan743x: fix for potential NULL pointer dereference with bare card
Date: Wed, 16 Dec 2020 04:35:04 +0300	[thread overview]
Message-ID: <1721393.xWxZJfhTyO@metabook> (raw)
In-Reply-To: <20201215171242.622435e8@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Wednesday, December 16, 2020 4:12:42 AM MSK Jakub Kicinski wrote:
> On Tue, 15 Dec 2020 23:39:14 +0000 patchwork-bot+netdevbpf@kernel.org
> 
> wrote:
> > Hello:
> > 
> > This patch was applied to bpf/bpf.git (refs/heads/master):
> > 
> > On Tue, 15 Dec 2020 19:12:45 +0300 you wrote:
> > > This is the 4th revision of the patch fix for potential null pointer
> > > dereference with lan743x card.
> > > 
> > > The simpliest way to reproduce: boot with bare lan743x and issue
> > > "ethtool ethN" command where ethN is the interface with lan743x card.
> > > Example:
> > > 
> > > $ sudo ethtool eth7
> > > dmesg:
...
> > > [...]
> > 
> > Here is the summary with links:
> >   - [v4] lan743x: fix for potential NULL pointer dereference with bare
> >   card
> >   
> >     https://git.kernel.org/bpf/bpf/c/e9e13b6adc33
> > 
> > You are awesome, thank you!
> > --
> > Deet-doot-dot, I am a bot.
> > https://korg.docs.kernel.org/patchwork/pwbot.html
> 
> Heh the bot got confused, I think.
> 
> What I meant when I said "let's wait for the merge window" was that
> the patch will not hit upstream until the merge window. It's now in
> Linus's tree. I'll make a submission of stable patches to Greg at the
> end of the week and I'll include this patch.
> 
> Thanks!

I think, firstly the bot was confused by me :-\
I should have asked you what exactly did you mean with "let's wait for the 
merge window"...
That's completely my fault, sorry for that.

                                Regards,
                                        Sergej.




      reply	other threads:[~2020-12-16  1:36 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
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 [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=1721393.xWxZJfhTyO@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=patchwork-bot+netdevbpf@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;
as well as URLs for NNTP newsgroup(s).