From: William Dauchy <william@gandi•net>
To: Jeff Kirsher <jeffrey.t.kirsher@intel•com>
Cc: intel-wired-lan@lists•osuosl.org, netdev@vger•kernel.org,
Emil Tantilov <emil.s.tantilov@intel•com>
Subject: dynamically set number of queues for 82598 devices in -stable
Date: Fri, 27 Nov 2015 11:05:57 +0100 [thread overview]
Message-ID: <20151127100557.GB21147@gandi.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 408 bytes --]
Hello Jeff,
I faced the problem described in commit 7e3f5c8:
ixgbe: fix bounds checking in ixgbe_setup_tc for 82598
This patch resolves an issue where users were not able to dynamically
set number of queues for 82598 via ethtool -L
I backported it for my v4.1.x build but I was wondering if this could be
a candidate for a backport in stable tree at least for v4.1.x.
Thanks,
--
William
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2015-11-27 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 10:05 William Dauchy [this message]
2016-03-25 15:22 ` dynamically set number of queues for 82598 devices in -stable William Dauchy
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=20151127100557.GB21147@gandi.net \
--to=william@gandi$(echo .)net \
--cc=emil.s.tantilov@intel$(echo .)com \
--cc=intel-wired-lan@lists$(echo .)osuosl.org \
--cc=jeffrey.t.kirsher@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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