From: kernel test robot <lkp@intel.com>
To: Markus Schneider-Pargmann <msp@baylibre.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v11 1/4] firmware: ti_sci: Add support for querying the firmware caps
Date: Sat, 31 Aug 2024 02:12:37 +0800 [thread overview]
Message-ID: <202408310239.suIrfaIB-lkp@intel.com> (raw)
In-Reply-To: <20240829201606.1407773-2-msp@baylibre.com>
Hi Markus,
kernel test robot noticed the following build warnings:
[auto build test WARNING on soc/for-next]
[also build test WARNING on linus/master v6.11-rc5 next-20240830]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Markus-Schneider-Pargmann/firmware-ti_sci-Add-support-for-querying-the-firmware-caps/20240830-041726
base: https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git for-next
patch link: https://lore.kernel.org/r/20240829201606.1407773-2-msp%40baylibre.com
patch subject: [PATCH v11 1/4] firmware: ti_sci: Add support for querying the firmware caps
config: arm-defconfig (https://download.01.org/0day-ci/archive/20240831/202408310239.suIrfaIB-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240831/202408310239.suIrfaIB-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202408310239.suIrfaIB-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/firmware/ti_sci.c:10:9: warning: 'pr_fmt' macro redefined [-Wmacro-redefined]
#define pr_fmt(fmt) "%s: " fmt, __func__
^
include/linux/printk.h:355:9: note: previous definition is here
#define pr_fmt(fmt) fmt
^
1 warning generated.
vim +/pr_fmt +10 drivers/firmware/ti_sci.c
aa276781a64a5f Nishanth Menon 2016-10-18 @10 #define pr_fmt(fmt) "%s: " fmt, __func__
aa276781a64a5f Nishanth Menon 2016-10-18 11
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-08-30 18:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 20:16 [PATCH v11 0/4] firmware: ti_sci: Introduce system suspend support Markus Schneider-Pargmann
2024-08-29 20:16 ` [PATCH v11 1/4] firmware: ti_sci: Add support for querying the firmware caps Markus Schneider-Pargmann
2024-08-30 4:29 ` Dhruva Gole
2024-08-30 18:12 ` kernel test robot [this message]
2024-08-31 2:27 ` kernel test robot
2024-08-29 20:16 ` [PATCH v11 2/4] firmware: ti_sci: Add system suspend and resume call Markus Schneider-Pargmann
2024-08-29 20:16 ` [PATCH v11 3/4] firmware: ti_sci: Introduce Power Management Ops Markus Schneider-Pargmann
2024-08-30 4:35 ` Dhruva Gole
2024-08-29 20:16 ` [PATCH v11 4/4] firmware: ti_sci: add CPU latency constraint management Markus Schneider-Pargmann
2024-09-03 0:54 ` Nathan Chancellor
2024-09-03 12:45 ` Nishanth Menon
2024-09-03 15:23 ` Markus Schneider-Pargmann
2024-09-01 20:30 ` [PATCH v11 0/4] firmware: ti_sci: Introduce system suspend support Nishanth Menon
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=202408310239.suIrfaIB-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=msp@baylibre.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.