From: kernel test robot <lkp@intel.com>
To: Gwendal Grignou <gwendal@chromium.org>, ukaszb@chromium.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
abhishekpandit@chromium.org, bleung@chromium.org,
chrome-platform@lists.linux.dev, dmitry.baryshkov@linaro.org,
gregkh@linuxfoundation.org, heikki.krogerus@linux.intel.com,
jthies@google.com, linux-usb@vger.kernel.org,
pholla@chromium.org, tzungbi@kernel.org,
Gwendal Grignou <gwendal@chromium.org>
Subject: Re: [PATCH] driver/platform/chrome: Update cros_ec_trace with new USCI commands
Date: Sun, 5 Jan 2025 00:27:32 +0800 [thread overview]
Message-ID: <202501050055.oR3g1RHJ-lkp@intel.com> (raw)
In-Reply-To: <20250103233407.4001046-1-gwendal@chromium.org>
Hi Gwendal,
kernel test robot noticed the following build errors:
[auto build test ERROR on chrome-platform/for-next]
[also build test ERROR on chrome-platform/for-firmware-next linus/master v6.13-rc5 next-20241220]
[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/Gwendal-Grignou/driver-platform-chrome-Update-cros_ec_trace-with-new-USCI-commands/20250104-073614
base: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
patch link: https://lore.kernel.org/r/20250103233407.4001046-1-gwendal%40chromium.org
patch subject: [PATCH] driver/platform/chrome: Update cros_ec_trace with new USCI commands
config: x86_64-buildonly-randconfig-005-20250104 (https://download.01.org/0day-ci/archive/20250105/202501050055.oR3g1RHJ-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250105/202501050055.oR3g1RHJ-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/202501050055.oR3g1RHJ-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/platform/chrome/cros_ec_trace.c:217:
In file included from drivers/platform/chrome/cros_ec_trace.h:83:
In file included from include/trace/define_trace.h:113:
In file included from include/trace/trace_events.h:256:
>> drivers/platform/chrome/cros_ec_trace.h:40:40: error: use of undeclared identifier 'EC_CMD_UCSI_PPM_SET'
40 | __print_symbolic(__entry->command, EC_CMDS),
| ^
drivers/platform/chrome/cros_ec_trace.c:169:15: note: expanded from macro 'EC_CMDS'
169 | TRACE_SYMBOL(EC_CMD_UCSI_PPM_SET), \
| ^
In file included from drivers/platform/chrome/cros_ec_trace.c:217:
In file included from drivers/platform/chrome/cros_ec_trace.h:83:
In file included from include/trace/define_trace.h:113:
In file included from include/trace/trace_events.h:256:
>> drivers/platform/chrome/cros_ec_trace.h:40:40: error: use of undeclared identifier 'EC_CMD_UCSI_PPM_GET'
drivers/platform/chrome/cros_ec_trace.c:170:15: note: expanded from macro 'EC_CMDS'
170 | TRACE_SYMBOL(EC_CMD_UCSI_PPM_GET), \
| ^
In file included from drivers/platform/chrome/cros_ec_trace.c:217:
In file included from drivers/platform/chrome/cros_ec_trace.h:83:
In file included from include/trace/define_trace.h:113:
In file included from include/trace/trace_events.h:256:
drivers/platform/chrome/cros_ec_trace.h:67:40: error: use of undeclared identifier 'EC_CMD_UCSI_PPM_SET'
67 | __print_symbolic(__entry->command, EC_CMDS),
| ^
drivers/platform/chrome/cros_ec_trace.c:169:15: note: expanded from macro 'EC_CMDS'
169 | TRACE_SYMBOL(EC_CMD_UCSI_PPM_SET), \
| ^
In file included from drivers/platform/chrome/cros_ec_trace.c:217:
In file included from drivers/platform/chrome/cros_ec_trace.h:83:
In file included from include/trace/define_trace.h:113:
In file included from include/trace/trace_events.h:256:
drivers/platform/chrome/cros_ec_trace.h:67:40: error: use of undeclared identifier 'EC_CMD_UCSI_PPM_GET'
drivers/platform/chrome/cros_ec_trace.c:170:15: note: expanded from macro 'EC_CMDS'
170 | TRACE_SYMBOL(EC_CMD_UCSI_PPM_GET), \
| ^
4 errors generated.
vim +/EC_CMD_UCSI_PPM_SET +40 drivers/platform/chrome/cros_ec_trace.h
58a2109f6eb46b Raul E Rangel 2019-04-16 20
205c9326fd8665 Raul E Rangel 2019-11-25 21 TRACE_EVENT(cros_ec_request_start,
58a2109f6eb46b Raul E Rangel 2019-04-16 22 TP_PROTO(struct cros_ec_command *cmd),
58a2109f6eb46b Raul E Rangel 2019-04-16 23 TP_ARGS(cmd),
58a2109f6eb46b Raul E Rangel 2019-04-16 24 TP_STRUCT__entry(
58a2109f6eb46b Raul E Rangel 2019-04-16 25 __field(uint32_t, version)
8143182426874a Gwendal Grignou 2020-08-14 26 __field(uint32_t, offset)
58a2109f6eb46b Raul E Rangel 2019-04-16 27 __field(uint32_t, command)
8143182426874a Gwendal Grignou 2020-08-14 28 __field(uint32_t, outsize)
8143182426874a Gwendal Grignou 2020-08-14 29 __field(uint32_t, insize)
58a2109f6eb46b Raul E Rangel 2019-04-16 30 ),
58a2109f6eb46b Raul E Rangel 2019-04-16 31 TP_fast_assign(
58a2109f6eb46b Raul E Rangel 2019-04-16 32 __entry->version = cmd->version;
3db0c9e5de7bd9 Tzung-Bi Shih 2022-06-09 33 __entry->offset = cmd->command / EC_CMD_PASSTHRU_OFFSET(CROS_EC_DEV_PD_INDEX);
3db0c9e5de7bd9 Tzung-Bi Shih 2022-06-09 34 __entry->command = cmd->command % EC_CMD_PASSTHRU_OFFSET(CROS_EC_DEV_PD_INDEX);
8143182426874a Gwendal Grignou 2020-08-14 35 __entry->outsize = cmd->outsize;
8143182426874a Gwendal Grignou 2020-08-14 36 __entry->insize = cmd->insize;
58a2109f6eb46b Raul E Rangel 2019-04-16 37 ),
8143182426874a Gwendal Grignou 2020-08-14 38 TP_printk("version: %u, offset: %d, command: %s, outsize: %u, insize: %u",
8143182426874a Gwendal Grignou 2020-08-14 39 __entry->version, __entry->offset,
8143182426874a Gwendal Grignou 2020-08-14 @40 __print_symbolic(__entry->command, EC_CMDS),
8143182426874a Gwendal Grignou 2020-08-14 41 __entry->outsize, __entry->insize)
58a2109f6eb46b Raul E Rangel 2019-04-16 42 );
58a2109f6eb46b Raul E Rangel 2019-04-16 43
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-01-04 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 13:10 [PATCH v12 0/2] usb: typec: Implement UCSI driver for ChromeOS Łukasz Bartosik
2024-12-31 13:10 ` [PATCH v12 1/2] platform/chrome: Update ChromeOS EC header for UCSI Łukasz Bartosik
2025-01-03 23:34 ` [PATCH] driver/platform/chrome: Update cros_ec_trace with new USCI commands Gwendal Grignou
2025-01-04 7:55 ` kernel test robot
2025-01-04 8:12 ` Greg KH
2025-01-06 18:43 ` Gwendal Grignou
2025-01-07 10:33 ` Greg KH
2025-01-04 16:27 ` kernel test robot [this message]
2024-12-31 13:10 ` [PATCH v12 2/2] usb: typec: ucsi: Implement ChromeOS UCSI driver Łukasz Bartosik
2025-01-07 10:28 ` Heikki Krogerus
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=202501050055.oR3g1RHJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=abhishekpandit@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=gwendal@chromium.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jthies@google.com \
--cc=linux-usb@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pholla@chromium.org \
--cc=tzungbi@kernel.org \
--cc=ukaszb@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