mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Heiko Schocher <hs@denx.de>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Heiko Schocher <hs@denx.de>,
	devicetree@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] regulator, dt: add dt support for tps6502x regulator
Date: Mon, 19 Oct 2015 15:14:36 +0800	[thread overview]
Message-ID: <201510191555.o18rGodH%fengguang.wu@intel.com> (raw)
In-Reply-To: <1445236033-27747-1-git-send-email-hs@denx.de>

Hi Heiko,

[auto build test WARNING on v4.3-rc6 -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url:    https://github.com/0day-ci/linux/commits/Heiko-Schocher/regulator-dt-add-dt-support-for-tps6502x-regulator/20151019-143244
reproduce:
        # apt-get install sparse
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> drivers/regulator/tps65023-regulator.c:363:1: sparse: symbol 'tps6502x_parse_dt_data' 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:[~2015-10-19  7:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19  7:14 kbuild test robot [this message]
2015-10-19  6:27 ` Heiko Schocher
2015-10-19  7:14   ` [RFC PATCH] regulator, dt: tps6502x_parse_dt_data() can be static kbuild test robot
2015-10-21 12:19   ` [PATCH] regulator, dt: add dt support for tps6502x regulator Mark Brown
2015-10-21 12:52     ` Heiko Schocher
2015-10-21 16:17       ` Mark Brown
2015-10-22  4:51         ` Heiko Schocher
2015-10-22 12:28           ` Mark Brown

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=201510191555.o18rGodH%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hs@denx.de \
    --cc=kbuild-all@01.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.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®