All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashwanth Goli <ashwanth@codeaurora.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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>
Subject: Re: linux-next: build warning after merge of the net tree
Date: Tue, 13 Jun 2017 17:01:52 +0530	[thread overview]
Message-ID: <cce358b0a2e9861141b0dfdac6b84859@codeaurora.org> (raw)
In-Reply-To: <20170613210845.24115319@canb.auug.org.au>

Hi Stephen,

On 2017-06-13 16:38, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the net tree, today's linux-next build (powerpc
> ppc44x_defconfig) produced this warning:
> 
> net/core/dev.c: In function 'dev_cpu_dead':
> net/core/dev.c:8330:2: warning: 'remsd' is used uninitialized in this
> function [-Wuninitialized]
>   net_rps_send_ipi(remsd);
>   ^
> 
> Introduced by commit
> 
>   773fc8f6e8d6 ("net: rps: send out pending IPI's on CPU hotplug")
> 
> These builds have CONFIG_RPS not set.

I have sent the fix patch to netdev mailing list.

  reply	other threads:[~2017-06-13 11:31 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 11:08 linux-next: build warning after merge of the net tree Stephen Rothwell
2017-06-13 11:31 ` Ashwanth Goli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-04 21:44 Stephen Rothwell
2019-12-05 22:57 ` David Miller
2019-12-05 23:48   ` Stephen Rothwell
2019-01-14  4:15 Stephen Rothwell
2018-08-21 22:04 Stephen Rothwell
2018-08-22 19:26 ` Cong Wang
2017-08-22 23:34 Stephen Rothwell
2017-01-18 22:56 Stephen Rothwell
2017-01-19  8:26 ` Tariq Toukan
2014-09-18  0:32 Stephen Rothwell
2014-09-18  0:32 ` Stephen Rothwell
2014-09-18  0:35 ` Randy Dunlap
2014-09-23 14:59   ` Michal Marek
2014-09-23 21:23     ` Stephen Rothwell
2014-09-24  0:36       ` Stephen Rothwell
2014-09-24  1:58       ` David Miller
2011-05-13  1:41 Stephen Rothwell
2011-05-13  1:41 ` Stephen Rothwell
2011-05-13  3:04 ` David Miller
2011-05-09  3:46 Stephen Rothwell
2011-05-09  3:46 ` Stephen Rothwell
2011-05-09  4:13 ` David Miller
2010-07-22  2:11 Stephen Rothwell
2010-07-22  2:11 ` Stephen Rothwell
2010-07-22  4:09 ` David Miller
2010-07-07  4:30 Stephen Rothwell
2010-07-07  4:30 ` Stephen Rothwell
2010-07-08  1:23 ` David Miller
2010-07-06  4:25 Stephen Rothwell
2010-07-06  4:25 ` Stephen Rothwell
2010-07-08  0:45 ` David Miller
2010-07-08  1:18   ` David Miller
2010-07-08  4:13     ` Joe Perches
2010-07-11  2:52       ` David Miller
2010-08-31  2:57 ` Stephen Rothwell
2010-08-31  2:57   ` Stephen Rothwell
2010-08-31  3:14   ` Joe Perches
2010-08-31  3:58     ` Stephen Rothwell
2010-08-31  4:03       ` Joe Perches
2010-08-31  4:46         ` David Miller
2010-08-31  4:45       ` David Miller
2010-08-31  4:42   ` David Miller
2010-03-01  5:47 Stephen Rothwell
2010-03-01  5:47 ` Stephen Rothwell
2010-03-01  7:02 ` David Miller
2010-02-15  3:32 Stephen Rothwell
2010-02-15  6:21 ` David Miller
2010-02-15  6:51 ` David Miller
2010-02-15  9:36   ` Jiri Pirko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cce358b0a2e9861141b0dfdac6b84859@codeaurora.org \
    --to=ashwanth@codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.