From: kernel test robot <lkp@intel.com>
To: Joshua Jayasingh <joshuajayasingh08@gmail.com>, groeck@chromium.org
Cc: oe-kbuild-all@lists.linux.dev, gregkh@linuxfoundation.org,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
Joshua Jayasingh <joshuajayasingh08@gmail.com>
Subject: Re: [PATCH] Subject: [PATCH] firmware: google: Add comments to coreboot_table.c
Date: Sun, 21 Sep 2025 23:54:33 +0800 [thread overview]
Message-ID: <202509212310.x4AI3ECo-lkp@intel.com> (raw)
In-Reply-To: <20250921132446.1974-1-joshuajayasingh08@gmail.com>
Hi Joshua,
kernel test robot noticed the following build warnings:
[auto build test WARNING on chrome-platform/for-next]
[also build test WARNING on chrome-platform/for-firmware-next linus/master v6.17-rc6]
[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/Joshua-Jayasingh/Subject-PATCH-firmware-google-Add-comments-to-coreboot_table-c/20250921-212952
base: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
patch link: https://lore.kernel.org/r/20250921132446.1974-1-joshuajayasingh08%40gmail.com
patch subject: [PATCH] Subject: [PATCH] firmware: google: Add comments to coreboot_table.c
config: riscv-randconfig-002-20250921 (https://download.01.org/0day-ci/archive/20250921/202509212310.x4AI3ECo-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 12.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250921/202509212310.x4AI3ECo-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/202509212310.x4AI3ECo-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/firmware/google/coreboot_table.c:140 bad line: _ to free the memory allocated for the coreboot_device.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-09-21 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-21 13:24 [PATCH] Subject: [PATCH] firmware: google: Add comments to coreboot_table.c Joshua Jayasingh
2025-09-21 13:35 ` Greg KH
2025-09-21 15:54 ` kernel test robot [this message]
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=202509212310.x4AI3ECo-lkp@intel.com \
--to=lkp@intel.com \
--cc=chrome-platform@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=joshuajayasingh08@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox