From: Matt Turner <mattst88@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 3/3] e1000e: Disable jumbo receive workaround on Lynx Point and newer
Date: Thu, 9 Nov 2017 13:40:42 -0800 [thread overview]
Message-ID: <CAEdQ38Fc1mSzXcN8KTjUMBRWsdPpj5K_ZWcBHDri7P4w+9B-JQ@mail.gmail.com> (raw)
In-Reply-To: <7c28a53a-0e23-e211-05ba-0a1891f8e9c5@intel.com>
On Thu, Nov 9, 2017 at 12:19 AM, Neftin, Sasha <sasha.neftin@intel.com> wrote:
> This patch should be rejected. The original patch 3e35d9918cbb ("e1000e:
> adjust PM QoS request") is from 2013, before Lynx Point and later devices
> were introduced. However, nothing was changed in this regard in the later
> devices and same limitation still apply.
Dang, that's unfortunate. Thanks for checking.
next prev parent reply other threads:[~2017-11-09 21:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 22:13 [Intel-wired-lan] [PATCH 1/3] e1000e: Set HTHRESH when PTHRESH is used Matt Turner
2017-11-07 22:13 ` [Intel-wired-lan] [PATCH 2/3] e1000e: Alert the user that C-states will be disabled by enabling jumbo frames Matt Turner
2017-11-09 9:36 ` Neftin, Sasha
2017-11-09 22:14 ` Shannon Nelson
2017-11-14 23:51 ` Matt Turner
2017-11-15 16:48 ` Shannon Nelson
2017-11-29 2:12 ` Brown, Aaron F
2017-11-07 22:13 ` [Intel-wired-lan] [PATCH 3/3] e1000e: Disable jumbo receive workaround on Lynx Point and newer Matt Turner
2017-11-09 8:19 ` Neftin, Sasha
2017-11-09 21:40 ` Matt Turner [this message]
2017-11-09 7:04 ` [Intel-wired-lan] [PATCH 1/3] e1000e: Set HTHRESH when PTHRESH is used Neftin, Sasha
2017-11-22 5:34 ` Brown, Aaron F
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=CAEdQ38Fc1mSzXcN8KTjUMBRWsdPpj5K_ZWcBHDri7P4w+9B-JQ@mail.gmail.com \
--to=mattst88@gmail.com \
--cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.