From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC v2 01/13] power: add power sequencer subsystem
Date: Sun, 29 Aug 2021 23:16:54 +0800 [thread overview]
Message-ID: <202108292354.t2t8ZTxf-lkp@intel.com> (raw)
In-Reply-To: <20210829131305.534417-2-dmitry.baryshkov@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2666 bytes --]
Hi Dmitry,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on robh/for-next]
[also build test WARNING on ath6kl/ath-next linus/master v5.14-rc7 next-20210827]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Dmitry-Baryshkov/create-power-sequencing-subsystem/20210829-212025
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: nds32-allyesconfig (attached as .config)
compiler: nds32le-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/bab71106910bdf6b8c567f385a9ac4e390cd67be
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Dmitry-Baryshkov/create-power-sequencing-subsystem/20210829-212025
git checkout bab71106910bdf6b8c567f385a9ac4e390cd67be
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=nds32
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/power/pwrseq/core.c:105:17: warning: no previous prototype for '__pwrseq_get' [-Wmissing-prototypes]
105 | struct pwrseq * __pwrseq_get(struct device *dev, const char *id, bool optional)
| ^~~~~~~~~~~~
vim +/__pwrseq_get +105 drivers/power/pwrseq/core.c
104
> 105 struct pwrseq * __pwrseq_get(struct device *dev, const char *id, bool optional)
106 {
107 struct pwrseq *pwrseq;
108 struct device_link *link;
109
110 pwrseq = _of_pwrseq_get(dev, id);
111 if (pwrseq == NULL)
112 return optional ? NULL : ERR_PTR(-ENODEV);
113 else if (IS_ERR(pwrseq))
114 return pwrseq;
115
116 if (!try_module_get(pwrseq->owner))
117 return ERR_PTR(-EPROBE_DEFER);
118
119 get_device(&pwrseq->dev);
120 link = device_link_add(dev, &pwrseq->dev, DL_FLAG_STATELESS);
121 if (!link)
122 dev_dbg(dev, "failed to create device link to %s\n",
123 dev_name(pwrseq->dev.parent));
124
125 return pwrseq;
126 }
127
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 60998 bytes --]
next prev parent reply other threads:[~2021-08-29 15:16 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 13:12 [RFC v2 00/13] create power sequencing subsystem Dmitry Baryshkov
2021-08-29 13:12 ` Dmitry Baryshkov
2021-08-29 13:12 ` [RFC v2 01/13] power: add power sequencer subsystem Dmitry Baryshkov
2021-08-29 13:12 ` Dmitry Baryshkov
2021-08-29 14:02 ` create power sequencing subsystem bluez.test.bot
2021-08-29 15:16 ` kernel test robot [this message]
2021-09-10 10:02 ` [RFC v2 01/13] power: add power sequencer subsystem Ulf Hansson
2021-09-10 10:02 ` Ulf Hansson
2021-09-13 12:32 ` Dmitry Baryshkov
2021-09-13 12:32 ` Dmitry Baryshkov
2021-09-13 13:42 ` Ulf Hansson
2021-09-13 13:42 ` Ulf Hansson
2021-08-29 13:12 ` [RFC v2 02/13] pwrseq: port MMC's pwrseq drivers to new pwrseq subsystem Dmitry Baryshkov
2021-08-29 13:12 ` Dmitry Baryshkov
2021-08-29 13:12 ` [RFC v2 03/13] mmc: core: switch " Dmitry Baryshkov
2021-08-29 13:12 ` Dmitry Baryshkov
2021-08-29 13:12 ` [RFC v2 04/13] pwrseq: add support for QCA BT+WiFi power sequencer Dmitry Baryshkov
2021-08-29 13:12 ` Dmitry Baryshkov
2021-08-30 22:29 ` kernel test robot
2021-08-29 13:12 ` [RFC v2 05/13] pwrseq: add fallback support Dmitry Baryshkov
2021-08-29 13:12 ` Dmitry Baryshkov
2021-08-29 13:12 ` [RFC v2 06/13] pwrseq: pwrseq_qca: implement " Dmitry Baryshkov
2021-08-29 13:12 ` Dmitry Baryshkov
2021-08-29 13:12 ` [RFC v2 07/13] Bluetooth: hci_qca: switch to using pwrseq Dmitry Baryshkov
2021-08-29 13:12 ` Dmitry Baryshkov
2021-08-29 13:13 ` [RFC v2 08/13] ath10k: add support for pwrseq sequencing Dmitry Baryshkov
2021-08-29 13:13 ` Dmitry Baryshkov
2021-08-29 13:13 ` [RFC v2 09/13] arm64: dts: qcom: sdm845-db845c: switch bt+wifi to qca power sequencer Dmitry Baryshkov
2021-08-29 13:13 ` Dmitry Baryshkov
2021-08-29 13:13 ` [RFC v2 10/13] arm64: dts: qcom: qrb5165-rb5: add bluetooth support Dmitry Baryshkov
2021-08-29 13:13 ` Dmitry Baryshkov
2021-08-29 13:13 ` [RFC v2 11/13] arm64: dts: qcom: sdm845-db845c: add second channel to qca power sequencer Dmitry Baryshkov
2021-08-29 13:13 ` Dmitry Baryshkov
2021-08-29 13:13 ` [RFC v2 12/13] WIP: PCI: qcom: use pwrseq to power up bus devices Dmitry Baryshkov
2021-08-29 13:13 ` Dmitry Baryshkov
2021-08-29 13:13 ` [RFC v2 13/13] WIP: arm64: dts: qcom: qrb5165-rb5: add bus-pwrseq property to pcie0 Dmitry Baryshkov
2021-08-29 13:13 ` Dmitry Baryshkov
2021-09-13 23:39 ` [RFC v2 00/13] create power sequencing subsystem Steev Klimaszewski
2021-09-13 23:39 ` Steev Klimaszewski
2021-10-06 3:49 ` Dmitry Baryshkov
2021-10-06 3:49 ` Dmitry Baryshkov
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=202108292354.t2t8ZTxf-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.