From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>
Cc: kai.heng.feng@canonical.com, netdev@vger.kernel.org,
nhorman@redhat.com, sassmann@redhat.com, aaron.f.brown@intel.com
Subject: Re: [net-next 6/6] e1000e: disable force K1-off feature
Date: Wed, 24 Jul 2019 13:52:16 -0700 [thread overview]
Message-ID: <8134ff55ff4b2c190adc48503dafdfde018fc84d.camel@intel.com> (raw)
In-Reply-To: <20190723.140444.1126474066269131522.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
On Tue, 2019-07-23 at 14:04 -0700, David Miller wrote:
> From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Date: Tue, 23 Jul 2019 10:36:50 -0700
>
> > diff --git a/drivers/net/ethernet/intel/e1000e/hw.h
> > b/drivers/net/ethernet/intel/e1000e/hw.h
> > index eff75bd8a8f0..e3c71fd093ee 100644
> > --- a/drivers/net/ethernet/intel/e1000e/hw.h
> > +++ b/drivers/net/ethernet/intel/e1000e/hw.h
> > @@ -662,6 +662,7 @@ struct e1000_dev_spec_ich8lan {
> > bool kmrn_lock_loss_workaround_enabled;
> > struct e1000_shadow_ram
> > shadow_ram[E1000_ICH8_SHADOW_RAM_WORDS];
> > bool nvm_k1_enabled;
> > + bool disable_k1_off;
> > bool eee_disable;
>
> I don't see any code actually setting this boolean, how does it work?
So either this patch is missing a bit of code OR this is not needed for
the Linux driver. Either way this patch needs changes or needs to be
dropped, so I am dropping this patch from the series until I get
further information from the client driver team.
I will be re-submitting this series, minus this patch.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-07-24 20:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 17:36 [net-next 0/6][pull request] 1GbE Intel Wired LAN Driver Updates 2019-07-23 Jeff Kirsher
2019-07-23 17:36 ` [net-next 1/6] igc: Remove the polarity field from a PHY information structure Jeff Kirsher
2019-07-23 17:36 ` [net-next 2/6] igc: Remove the unused field from a device specification structure Jeff Kirsher
2019-07-23 17:36 ` [net-next 3/6] igc: Update the MAC reset flow Jeff Kirsher
2019-07-23 17:36 ` [net-next 4/6] igc: Add more SKUs for i225 device Jeff Kirsher
2019-07-23 17:36 ` [net-next 5/6] e1000e: add workaround for possible stalled packet Jeff Kirsher
2019-07-23 17:36 ` [net-next 6/6] e1000e: disable force K1-off feature Jeff Kirsher
2019-07-23 21:04 ` David Miller
2019-07-24 2:30 ` Jeff Kirsher
2019-07-24 20:52 ` Jeff Kirsher [this message]
2019-07-23 21:16 ` [net-next 0/6][pull request] 1GbE Intel Wired LAN Driver Updates 2019-07-23 Saeed Mahameed
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=8134ff55ff4b2c190adc48503dafdfde018fc84d.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=aaron.f.brown@intel.com \
--cc=davem@davemloft.net \
--cc=kai.heng.feng@canonical.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@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