From: kernel test robot <lkp@intel.com>
To: Guangshuo Li <lgs201920130244@gmail.com>,
Benson Leung <bleung@chromium.org>,
Tzung-Bi Shih <tzungbi@kernel.org>,
Olof Johansson <olof@lixom.net>,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Guangshuo Li <lgs201920130244@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] platform/chrome: fix reference leak on failed device registration
Date: Fri, 17 Apr 2026 15:51:42 +0800 [thread overview]
Message-ID: <202604171521.d1s0T0Dr-lkp@intel.com> (raw)
In-Reply-To: <20260415175038.3633384-1-lgs201920130244@gmail.com>
Hi Guangshuo,
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 v7.0 next-20260416]
[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/Guangshuo-Li/platform-chrome-fix-reference-leak-on-failed-device-registration/20260416-135638
base: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
patch link: https://lore.kernel.org/r/20260415175038.3633384-1-lgs201920130244%40gmail.com
patch subject: [PATCH] platform/chrome: fix reference leak on failed device registration
config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20260417/202604171521.d1s0T0Dr-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260417/202604171521.d1s0T0Dr-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/202604171521.d1s0T0Dr-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/platform/chrome/chromeos_pstore.c: In function 'chromeos_pstore_init':
>> drivers/platform/chrome/chromeos_pstore.c:131:17: error: 'ret' undeclared (first use in this function)
131 | ret = platform_device_register(&chromeos_ramoops);
| ^~~
drivers/platform/chrome/chromeos_pstore.c:131:17: note: each undeclared identifier is reported only once for each function it appears in
vim +/ret +131 drivers/platform/chrome/chromeos_pstore.c
119
120 static int __init chromeos_pstore_init(void)
121 {
122 bool acpi_dev_found;
123
124 if (ecc_size > 0)
125 chromeos_ramoops_data.ecc_info.ecc_size = ecc_size;
126
127 /* First check ACPI for non-hardcoded values from firmware. */
128 acpi_dev_found = chromeos_check_acpi();
129
130 if (acpi_dev_found || dmi_check_system(chromeos_pstore_dmi_table)) {
> 131 ret = platform_device_register(&chromeos_ramoops);
132 if (ret)
133 platform_device_put(&chromeos_ramoops);
134
135 return ret;
136 }
137
138 return -ENODEV;
139 }
140
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-04-17 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 17:50 [PATCH] platform/chrome: fix reference leak on failed device registration Guangshuo Li
2026-04-15 21:47 ` Olof Johansson
2026-04-16 9:26 ` Guangshuo Li
2026-04-16 10:21 ` Guangshuo Li
2026-04-17 7:51 ` kernel test robot [this message]
2026-04-17 8:46 ` kernel test robot
2026-04-17 9:11 ` Guangshuo Li
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=202604171521.d1s0T0Dr-lkp@intel.com \
--to=lkp@intel.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=olof@lixom.net \
--cc=stable@vger.kernel.org \
--cc=tzungbi@kernel.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