From: Kurt Kanzenbach <kurt@linutronix.de>
To: "Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"kuba@kernel.org" <kuba@kernel.org>
Cc: "Karlsson, Magnus" <magnus.karlsson@intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"vinschen@redhat.com" <vinschen@redhat.com>,
"john.fastabend@gmail.com" <john.fastabend@gmail.com>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"Fijalkowski, Maciej" <maciej.fijalkowski@intel.com>,
"hawk@kernel.org" <hawk@kernel.org>,
"ast@kernel.org" <ast@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>
Subject: Re: [PATCH net-next 0/2][pull request] 1GbE Intel Wired LAN Driver Updates 2022-02-07
Date: Wed, 09 Feb 2022 19:22:53 +0100 [thread overview]
Message-ID: <877da32936.fsf@kurt> (raw)
In-Reply-To: <699b8636cafcfa82a99cf290e3cffbab91b6afbb.camel@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
On Wed Feb 09 2022, Anthony L. Nguyen wrote:
> On Wed, 2022-02-09 at 09:13 +0100, Kurt Kanzenbach wrote:
>> Hi Tony,
>>
>> On Tue Feb 08 2022, Jakub Kicinski wrote:
>> > On Mon, 7 Feb 2022 15:32:44 -0800 Tony Nguyen wrote:
>> > > Corinna Vinschen says:
>> > >
>> > > Fix the kernel warning "Missing unregister, handled but fix
>> > > driver"
>> > > when running, e.g.,
>> > >
>> > > $ ethtool -G eth0 rx 1024
>> > >
>> > > on igc. Remove memset hack from igb and align igb code to igc.
>> >
>> > Why -next?
>
> As the original submission was targeting -next, I carried that forward.
> Since the warning said it was handled, I thought it was ok to go there.
>
>> Can we get these patches into net, please? The mentioned igc problem
>> exists on v5.15-LTS too.
>
> I'll follow the igc patch and submit a request to stable when it hits
> Linus' tree.
OK, thanks!
> For igb, as it sounds like things are working, just not
> with the preferred method, so I don't plan on sending that to stable.
> Or is there an issue there that this patch needs to go to stable as
> well?
igb is fine, as it uses the memset() approach.
Thanks,
Kurt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2022-02-09 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 23:32 [PATCH net-next 0/2][pull request] 1GbE Intel Wired LAN Driver Updates 2022-02-07 Tony Nguyen
2022-02-07 23:32 ` [PATCH net-next 1/2] igc: avoid kernel warning when changing RX ring parameters Tony Nguyen
2022-02-07 23:32 ` [PATCH net-next 2/2] igb: refactor XDP registration Tony Nguyen
2022-02-09 5:13 ` [PATCH net-next 0/2][pull request] 1GbE Intel Wired LAN Driver Updates 2022-02-07 Jakub Kicinski
2022-02-09 8:13 ` Kurt Kanzenbach
2022-02-09 17:20 ` Nguyen, Anthony L
2022-02-09 18:22 ` Kurt Kanzenbach [this message]
2022-02-09 12:00 ` patchwork-bot+netdevbpf
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=877da32936.fsf@kurt \
--to=kurt@linutronix.de \
--cc=anthony.l.nguyen@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=vinschen@redhat.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).