netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Lowe <nick.lowe@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Matt Corallo <linux-wired-list@bluematt.me>,
	"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>
Subject: Re: [PATCH net] igb: Enable RSS for Intel I211 Ethernet Controller
Date: Mon, 3 May 2021 13:32:24 +0100	[thread overview]
Message-ID: <CADSoG1sf9zXj9CQfJ3kQ1_CUapmZDa6ZeKtbspUsm34c7TSKqw@mail.gmail.com> (raw)
In-Reply-To: <20210201123350.159feabd@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

Hi all,

Now that the 5.12 kernel has released, please may we consider
backporting commit 6e6026f2dd2005844fb35c3911e8083c09952c6c to both
the 5.4 and 5.10 LTS kernels so that RSS starts to function with the
i211?

Best,

Nick

  reply	other threads:[~2021-05-03 12:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21 22:25 [PATCH net] igb: Enable RSS for Intel I211 Ethernet Controller Nick Lowe
2021-01-31 23:17 ` Matt Corallo
2021-02-01 16:47   ` Jakub Kicinski
2021-02-01 18:32     ` Nguyen, Anthony L
2021-02-01 19:45       ` Jakub Kicinski
2021-02-01 20:06         ` Nick Lowe
2021-02-01 20:21         ` Matt Corallo
2021-02-01 20:23           ` Nick Lowe
2021-02-01 20:33             ` Jakub Kicinski
2021-05-03 12:32               ` Nick Lowe [this message]
2021-05-03 18:30                 ` Jakub Kicinski
2021-05-03 19:53                   ` Stable inclusion request - " Nick Lowe
2021-05-04  4:43                     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2020-12-21 19:15 [PATCH net] " Nick Lowe
2020-12-21 22:11 ` Jakub Kicinski

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=CADSoG1sf9zXj9CQfJ3kQ1_CUapmZDa6ZeKtbspUsm34c7TSKqw@mail.gmail.com \
    --to=nick.lowe@gmail.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-wired-list@bluematt.me \
    --cc=netdev@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).