From: kernel test robot <lkp@intel.com>
To: Sumit Gupta <sumitg@nvidia.com>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, robh+dt@kernel.org
Cc: kbuild-all@lists.01.org, sumitg@nvidia.com, bbasu@nvidia.com,
vsethi@nvidia.com, jsequeira@nvidia.com
Subject: Re: [Patch v2 5/9] soc: tegra: cbb: Add CBB1.0 driver for Tegra194
Date: Sat, 18 Dec 2021 05:13:48 +0800 [thread overview]
Message-ID: <202112180528.6oINgaDF-lkp@intel.com> (raw)
In-Reply-To: <20211217120656.16480-6-sumitg@nvidia.com>
Hi Sumit,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on robh/for-next]
[also build test WARNING on tegra-drm/drm/tegra/for-next v5.16-rc5 next-20211217]
[cannot apply to tegra/for-next]
[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/Sumit-Gupta/CBB-driver-for-Tegra194-Tegra234-Tegra-Grace/20211217-200840
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: arm64-allyesconfig (https://download.01.org/0day-ci/archive/20211218/202112180528.6oINgaDF-lkp@intel.com/config)
compiler: aarch64-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/4289c950622627160bdc937ad22a311db38f4ca8
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Sumit-Gupta/CBB-driver-for-Tegra194-Tegra234-Tegra-Grace/20211217-200840
git checkout 4289c950622627160bdc937ad22a311db38f4ca8
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/soc/tegra/cbb/
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/soc/tegra/cbb/tegra-cbb.c: In function 'print_cbb_err':
>> drivers/soc/tegra/cbb/tegra-cbb.c:31:17: warning: function 'print_cbb_err' might be a candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
31 | seq_vprintf(file, fmt, args);
| ^~~~~~~~~~~
vim +31 drivers/soc/tegra/cbb/tegra-cbb.c
22
23 void print_cbb_err(struct seq_file *file, const char *fmt, ...)
24 {
25 va_list args;
26 struct va_format vaf;
27
28 va_start(args, fmt);
29
30 if (file) {
> 31 seq_vprintf(file, fmt, args);
32 } else {
33 vaf.fmt = fmt;
34 vaf.va = &args;
35 pr_crit("%pV", &vaf);
36 }
37
38 va_end(args);
39 }
40
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2021-12-17 21:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 12:06 [Patch v2 0/9] CBB driver for Tegra194, Tegra234 & Tegra-Grace Sumit Gupta
2021-12-17 12:06 ` [Patch v2 1/9] soc: tegra: set ERD bit to mask inband errors Sumit Gupta
2021-12-17 12:06 ` [Patch v2 2/9] dt-bindings: arm: tegra: Add NVIDIA Tegra194 CBB1.0 binding Sumit Gupta
2021-12-17 12:06 ` [Patch v2 3/9] dt-bindings: arm: tegra: Add NVIDIA Tegra194 axi2apb binding Sumit Gupta
2021-12-17 12:06 ` [Patch v2 4/9] arm64: tegra: Add node for CBB1.0 in Tegra194 SOC Sumit Gupta
2021-12-17 12:06 ` [Patch v2 5/9] soc: tegra: cbb: Add CBB1.0 driver for Tegra194 Sumit Gupta
2021-12-17 21:13 ` kernel test robot [this message]
2021-12-17 12:06 ` [Patch v2 6/9] dt-bindings: arm: tegra: Add NVIDIA Tegra234 CBB2.0 binding Sumit Gupta
2021-12-17 12:06 ` [Patch v2 7/9] arm64: tegra: Add node for CBB2.0 in Tegra234 SOC Sumit Gupta
2021-12-17 12:06 ` [Patch v2 8/9] soc: tegra: cbb: Add driver for Tegra234 CBB2.0 Sumit Gupta
2021-12-18 0:07 ` kernel test robot
2021-12-17 12:06 ` [Patch v2 9/9] soc: tegra: cbb: Add support for tegra-grace SOC Sumit Gupta
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=202112180528.6oINgaDF-lkp@intel.com \
--to=lkp@intel.com \
--cc=bbasu@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=jsequeira@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sumitg@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=vsethi@nvidia.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;
as well as URLs for NNTP newsgroup(s).