[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1437529280.16792.9.camel@ellerman.id.au>
Date: Wed, 22 Jul 2015 11:41:20 +1000
From: Michael Ellerman <mpe@...erman.id.au>
To: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Cc: "Avargil, Raanan" <raanan.avargil@...el.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
intel-wired-lan@...ts.osuosl.org, aaron.f.brown@...el.com,
yanirx.lubetkin@...el.com, jesse.brandeburg@...el.com,
shannon.nelson@...el.com, carolyn.wyborny@...el.com,
donald.c.skidmore@...el.com, matthew.vick@...el.com,
john.ronciak@...el.com, mitch.a.williams@...el.com
Subject: Re: [PATCH] e1000e: Move e1000e_disable_aspm_locked() inside
CONFIG_PM
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 e1000e_disable_aspm_locked().
> >
> > Move it inside the existing CONFIG_PM block to avoid the warning.
> >
> > Signed-off-by: Michael Ellerman <mpe@...erman.id.au>
> > ---
> > drivers/net/ethernet/intel/e1000e/netdev.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> NACK, this is already fixed in my next-queue tree. Raanan submitted a
> patch back on July 6th to resolve this issue, see commit id
> a75787d2246a93d256061db602f252703559af65 in my dev-queue branch of my
> next-queue tree.
OK. I take it your next-queue is destined for 4.3, so we'll just have to suck
on the warning until then?
cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists