[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190723.140444.1126474066269131522.davem@davemloft.net>
Date: Tue, 23 Jul 2019 14:04:44 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jeffrey.t.kirsher@...el.com
Cc: kai.heng.feng@...onical.com, netdev@...r.kernel.org,
nhorman@...hat.com, sassmann@...hat.com, aaron.f.brown@...el.com
Subject: Re: [net-next 6/6] e1000e: disable force K1-off feature
From: Jeff Kirsher <jeffrey.t.kirsher@...el.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?
Powered by blists - more mailing lists