lkml.org 
[lkml]   [2020]   [Jun]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: linux-next: build warning after merge of the net-next tree
Date
> -----Original Message-----
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Sent: Friday, June 12, 2020 18:16
> To: Kirsher, Jeffrey T <jeffrey.t.kirsher@intel.com>
> Cc: David Miller <davem@davemloft.net>; Networking
> <netdev@vger.kernel.org>; Linux Next Mailing List <linux-
> next@vger.kernel.org>; Linux Kernel Mailing List <linux-
> kernel@vger.kernel.org>; Lifshits, Vitaly <vitaly.lifshits@intel.com>
> Subject: Re: linux-next: build warning after merge of the net-next tree
>
> Hi all,
>
> On Wed, 27 May 2020 01:15:09 +0000 "Kirsher, Jeffrey T"
> <jeffrey.t.kirsher@intel.com> wrote:
> >
> > > -----Original Message-----
> > > From: Stephen Rothwell <sfr@canb.auug.org.au>
> > > Sent: Monday, May 25, 2020 05:40
> > > To: David Miller <davem@davemloft.net>; Networking
> > > <netdev@vger.kernel.org>
> > > Cc: Linux Next Mailing List <linux-next@vger.kernel.org>; Linux
> > > Kernel Mailing List <linux-kernel@vger.kernel.org>; Lifshits, Vitaly
> > > <vitaly.lifshits@intel.com>; Kirsher, Jeffrey T
> > > <jeffrey.t.kirsher@intel.com>
> > > Subject: linux-next: build warning after merge of the net-next tree
> > >
> > > Hi all,
> > >
> > > After merging the net-next tree, today's linux-next build (sparc64
> > > defconfig) produced this warning:
> > >
> > > drivers/net/ethernet/intel/e1000e/netdev.c:137:13: warning:
> 'e1000e_check_me'
> > > defined but not used [-Wunused-function] static bool
> > > e1000e_check_me(u16
> > > device_id)
> > > ^~~~~~~~~~~~~~~
> > >
> > > Introduced by commit
> > >
> > > e086ba2fccda ("e1000e: disable s0ix entry and exit flows for ME
> > > systems")
> > >
> > > CONFIG_PM_SLEEP is not set for this build.
> > >
> > [Kirsher, Jeffrey T]
> >
> > Vitaly informed me that he has a fix that he will be sending me, I will make
> sure to expedite it.
>
> I am still getting this warning.

I apologize, I have not seen a fix from Vitaly, that I am aware of. I will make sure you have a patch before Monday.

\
 
 \ /
  Last update: 2020-06-13 03:21    [W:0.087 / U:0.116 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site