From: kernel test robot <lkp@intel.com>
To: Triet Hoang <triet.hoang.dev@gmail.com>,
Maxim Levitsky <maximlevitsky@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, Alex Dubov <oakad@yahoo.com>,
Ulf Hansson <ulfh@kernel.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Triet Hoang <triet.hoang.dev@gmail.com>
Subject: Re: [PATCH] memstick: Convert to DEFINE_SIMPLE_DEV_PM_OPS()
Date: Wed, 26 Aug 2026 04:13:05 +0800 [thread overview]
Message-ID: <202608260448.DBZikir0-lkp@intel.com> (raw)
In-Reply-To: <20260825082718.244949-1-triet.hoang.dev@gmail.com>
Hi Triet,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v7.2 next-20260824]
[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/Triet-Hoang/memstick-Convert-to-DEFINE_SIMPLE_DEV_PM_OPS/20260825-152717
base: linus/master
patch link: https://lore.kernel.org/r/20260825082718.244949-1-triet.hoang.dev%40gmail.com
patch subject: [PATCH] memstick: Convert to DEFINE_SIMPLE_DEV_PM_OPS()
config: csky-allmodconfig (https://download.01.org/0day-ci/archive/20260826/202608260448.DBZikir0-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260826/202608260448.DBZikir0-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/202608260448.DBZikir0-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/memstick/host/r592.c: In function 'r592_suspend':
>> drivers/memstick/host/r592.c:854:9: error: implicit declaration of function 'r592_clear_interrupts' [-Wimplicit-function-declaration]
854 | r592_clear_interrupts(dev);
| ^~~~~~~~~~~~~~~~~~~~~
vim +/r592_clear_interrupts +854 drivers/memstick/host/r592.c
9263412501022fe Maxim Levitsky 2011-03-25 849
9263412501022fe Maxim Levitsky 2011-03-25 850 static int r592_suspend(struct device *core_dev)
9263412501022fe Maxim Levitsky 2011-03-25 851 {
deaa53989537c62 Chuhong Yuan 2019-07-23 852 struct r592_device *dev = dev_get_drvdata(core_dev);
9263412501022fe Maxim Levitsky 2011-03-25 853
9263412501022fe Maxim Levitsky 2011-03-25 @854 r592_clear_interrupts(dev);
9263412501022fe Maxim Levitsky 2011-03-25 855 memstick_suspend_host(dev->host);
8fa7292fee5c524 Thomas Gleixner 2025-04-05 856 timer_delete_sync(&dev->detect_timer);
9263412501022fe Maxim Levitsky 2011-03-25 857 return 0;
9263412501022fe Maxim Levitsky 2011-03-25 858 }
9263412501022fe Maxim Levitsky 2011-03-25 859
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-08-25 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 8:27 [PATCH] memstick: Convert to DEFINE_SIMPLE_DEV_PM_OPS() Triet Hoang
2026-08-25 20:13 ` kernel test robot [this message]
2026-08-26 2:14 ` kernel test robot
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=202608260448.DBZikir0-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=oakad@yahoo.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=triet.hoang.dev@gmail.com \
--cc=ulfh@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