[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160728221350.GA22625@electric-eye.fr.zoreil.com>
Date: Fri, 29 Jul 2016 00:13:50 +0200
From: Francois Romieu <romieu@...zoreil.com>
To: Hau <hau@...ltek.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
nic_swsd <nic_swsd@...ltek.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net 1/3] r8169:fix kernel log spam when set or get
hardware wol setting.
Hau <hau@...ltek.com> :
[...]
> > Either the driver resumes the device so that it can perform requested
> > operation or it signals .set_wol failure when the device is suspended.
> >
> > If the driver does something else, "spam removal" translates to "silent
> > failure".
>
> Because "tp->saved_wolopts" will be used to set hardware wol capability in
> rtl8169_runtime_resume(). So I prefer to keep "wol->wolopts" to
> " tp->saved_wolopts " in runtime suspend state and set this to this
> "wol->wolopts" to hardware in in rtl8169_runtime_resume().
It would be fine if it could be proven that rtl8169_runtime_resume() will
always be run before software state is lost.
--
Ueimor
Powered by blists - more mailing lists