On Thu, 2015-07-23 at 07:07 -0700, Jeff Kirsher wrote:
On Wed, 2015-07-22 at 11:41 +1000, Michael Ellerman wrote:
On Wed, 2015-07-15 at 03:30 -0700, Jeff Kirsher wrote:
On Tue, 2015-07-14 at 13:54 +1000, Michael Ellerman wrote:
e1000e_disable_aspm_locked() is only used in
On Wed, 2015-07-22 at 11:41 +1000, Michael Ellerman wrote:
On Wed, 2015-07-15 at 03:30 -0700, Jeff Kirsher wrote:
On Tue, 2015-07-14 at 13:54 +1000, Michael Ellerman wrote:
e1000e_disable_aspm_locked() is only used in __e1000_resume()
which is
inside CONFIG_PM. So when CONFIG_PM=n we get
On Wed, 2015-07-15 at 03:30 -0700, Jeff Kirsher wrote:
On Tue, 2015-07-14 at 13:54 +1000, Michael Ellerman wrote:
e1000e_disable_aspm_locked() is only used in __e1000_resume() which is
inside CONFIG_PM. So when CONFIG_PM=n we get a defined but not used
warning for
On Tue, 2015-07-14 at 13:54 +1000, Michael Ellerman wrote:
e1000e_disable_aspm_locked() is only used in __e1000_resume() which is
inside CONFIG_PM. So when CONFIG_PM=n we get a defined but not used
warning for e1000e_disable_aspm_locked().
Move it inside the existing CONFIG_PM block to avoid
e1000e_disable_aspm_locked() is only used in __e1000_resume() which is
inside CONFIG_PM. So when CONFIG_PM=n we get a defined but not used
warning for e1000e_disable_aspm_locked().
Move it inside the existing CONFIG_PM block to avoid the warning.
Signed-off-by: Michael Ellerman
