mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	tipbuild@zytor.com, Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@kernel.org>
Subject: [tip:timers/core 5/5] kernel/time/tick-broadcast.c:441:6: sparse: symbol 'tick_shutdown_broadcast' was not declared. Should it be static?
Date: Sun, 24 Mar 2019 01:04:05 +0800	[thread overview]
Message-ID: <201903240149.MYxIj3WB%lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/core
head:   973f88ca8b159592685b6ccedb0b91db376bf20d
commit: 973f88ca8b159592685b6ccedb0b91db376bf20d [5/5] tick: Remove outgoing CPU from broadcast masks
reproduce:
        # apt-get install sparse
        git checkout 973f88ca8b159592685b6ccedb0b91db376bf20d
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'


sparse warnings: (new ones prefixed by >>)

>> kernel/time/tick-broadcast.c:441:6: sparse: symbol 'tick_shutdown_broadcast' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

             reply	other threads:[~2019-03-23 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-23 17:04 kbuild test robot [this message]
2019-03-23 17:04 ` [RFC PATCH tip] tick: tick_shutdown_broadcast() can be static kbuild test robot
2019-03-23 17:23   ` Thomas Gleixner

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=201903240149.MYxIj3WB%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=fweisbec@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tipbuild@zytor.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®