[chrome-platform-linux:for-next 14/16] drivers/platform/chrome/cros_ec_debugfs.c:288:30: sparse: sparse: symbol 'cros_ec_uptime_fops' was not declared. Should it be static?

mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed

From: kbuild test robot <lkp@intel.com>
To: Tim Wawrzynczak <twawrzynczak@chromium.org>
Cc: kbuild-all@01.org,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Benson Leung <bleung@chromium.org>,
	Guenter Roeck <groeck@chromium.org>,
	linux-kernel@vger.kernel.org
Subject: [chrome-platform-linux:for-next 14/16] drivers/platform/chrome/cros_ec_debugfs.c:288:30: sparse: sparse: symbol 'cros_ec_uptime_fops' was not declared. Should it be static?
Date: Sat, 15 Jun 2019 18:55:11 +0800	[thread overview]
Message-ID: <201906151827.DYouSmoA%lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
head:   3185b85f64fcb5bf521a4093b13ad901569d09c7
commit: 909447f683b31d27b8d59838f8723d744f9300a2 [14/16] platform/chrome: cros_ec_debugfs: Add debugfs entry to retrieve EC uptime
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-rc1-7-g2b96cd8-dirty
        git checkout 909447f683b31d27b8d59838f8723d744f9300a2
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)


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

next             reply	other threads:[~2019-06-15 10:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-15 10:55 kbuild test robot [this message]
2019-06-15 10:55 ` [RFC PATCH chrome-platform-linux] platform/chrome: cros_ec_debugfs: cros_ec_uptime_fops can be static kbuild test robot
2019-06-18  8:35   ` Enric Balletbo i Serra

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=201906151827.DYouSmoA%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bleung@chromium.org \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=twawrzynczak@chromium.org \
    /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®