From: kernel test robot <lkp@intel.com>
To: Hongjie Fang <hongjiefang@asrmicro.com>,
alim.akhtar@samsung.com, avri.altman@wdc.com, bvanassche@acm.org,
James.Bottomley@hansenpartnership.com,
martin.petersen@oracle.com
Cc: oe-kbuild-all@lists.linux.dev, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] scsi: ufs: core: call hibern8 notify when hibern8 cmd failed
Date: Sat, 2 May 2026 18:05:26 +0800 [thread overview]
Message-ID: <202605021742.XyNEfM7G-lkp@intel.com> (raw)
In-Reply-To: <20260430042212.3712251-1-hongjiefang@asrmicro.com>
Hi Hongjie,
kernel test robot noticed the following build warnings:
[auto build test WARNING on jejb-scsi/for-next]
[also build test WARNING on mkp-scsi/for-next linus/master v7.1-rc1 next-20260430]
[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/Hongjie-Fang/scsi-ufs-core-call-hibern8-notify-when-hibern8-cmd-failed/20260501-050358
base: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
patch link: https://lore.kernel.org/r/20260430042212.3712251-1-hongjiefang%40asrmicro.com
patch subject: [PATCH v3] scsi: ufs: core: call hibern8 notify when hibern8 cmd failed
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20260502/202605021742.XyNEfM7G-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260502/202605021742.XyNEfM7G-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/202605021742.XyNEfM7G-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/ufs/host/ufs-exynos.c: In function 'exynos_ufs_hce_enable_notify':
>> drivers/ufs/host/ufs-exynos.c:1614:9: warning: enumeration value 'ROLLBACK_CHANGE' not handled in switch [-Wswitch]
1614 | switch (status) {
| ^~~~~~
drivers/ufs/host/ufs-exynos.c: In function 'exynos_ufs_link_startup_notify':
drivers/ufs/host/ufs-exynos.c:1654:9: warning: enumeration value 'ROLLBACK_CHANGE' not handled in switch [-Wswitch]
1654 | switch (status) {
| ^~~~~~
drivers/ufs/host/ufs-exynos.c: In function 'exynos_ufs_pwr_change_notify':
drivers/ufs/host/ufs-exynos.c:1687:9: warning: enumeration value 'ROLLBACK_CHANGE' not handled in switch [-Wswitch]
1687 | switch (status) {
| ^~~~~~
vim +/ROLLBACK_CHANGE +1614 drivers/ufs/host/ufs-exynos.c
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1607
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1608 static int exynos_ufs_hce_enable_notify(struct ufs_hba *hba,
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1609 enum ufs_notify_change_status status)
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1610 {
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1611 struct exynos_ufs *ufs = ufshcd_get_variant(hba);
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1612 int ret = 0;
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1613
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 @1614 switch (status) {
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1615 case PRE_CHANGE:
9a80bc5debf74b0 drivers/ufs/host/ufs-exynos.c Bart Van Assche 2023-01-12 1616 /*
9a80bc5debf74b0 drivers/ufs/host/ufs-exynos.c Bart Van Assche 2023-01-12 1617 * The maximum segment size must be set after scsi_host_alloc()
9a80bc5debf74b0 drivers/ufs/host/ufs-exynos.c Bart Van Assche 2023-01-12 1618 * has been called and before LUN scanning starts
9a80bc5debf74b0 drivers/ufs/host/ufs-exynos.c Bart Van Assche 2023-01-12 1619 * (ufshcd_async_scan()). Note: this callback may also be called
9a80bc5debf74b0 drivers/ufs/host/ufs-exynos.c Bart Van Assche 2023-01-12 1620 * from other functions than ufshcd_init().
9a80bc5debf74b0 drivers/ufs/host/ufs-exynos.c Bart Van Assche 2023-01-12 1621 */
c96499fcb403b18 drivers/ufs/host/ufs-exynos.c Eric Biggers 2024-07-08 1622 hba->host->max_segment_size = DATA_UNIT_SIZE;
9a80bc5debf74b0 drivers/ufs/host/ufs-exynos.c Bart Van Assche 2023-01-12 1623
52e5035f7b079be drivers/scsi/ufs/ufs-exynos.c Chanho Park 2021-10-18 1624 if (ufs->drv_data->pre_hce_enable) {
52e5035f7b079be drivers/scsi/ufs/ufs-exynos.c Chanho Park 2021-10-18 1625 ret = ufs->drv_data->pre_hce_enable(ufs);
52e5035f7b079be drivers/scsi/ufs/ufs-exynos.c Chanho Park 2021-10-18 1626 if (ret)
52e5035f7b079be drivers/scsi/ufs/ufs-exynos.c Chanho Park 2021-10-18 1627 return ret;
52e5035f7b079be drivers/scsi/ufs/ufs-exynos.c Chanho Park 2021-10-18 1628 }
52e5035f7b079be drivers/scsi/ufs/ufs-exynos.c Chanho Park 2021-10-18 1629
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1630 ret = exynos_ufs_host_reset(hba);
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1631 if (ret)
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1632 return ret;
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1633 exynos_ufs_dev_hw_reset(hba);
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1634 break;
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1635 case POST_CHANGE:
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1636 exynos_ufs_calc_pwm_clk_div(ufs);
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1637 if (!(ufs->opts & EXYNOS_UFS_OPT_BROKEN_AUTO_CLK_CTRL))
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1638 exynos_ufs_enable_auto_ctrl_hcc(ufs);
52e5035f7b079be drivers/scsi/ufs/ufs-exynos.c Chanho Park 2021-10-18 1639
52e5035f7b079be drivers/scsi/ufs/ufs-exynos.c Chanho Park 2021-10-18 1640 if (ufs->drv_data->post_hce_enable)
52e5035f7b079be drivers/scsi/ufs/ufs-exynos.c Chanho Park 2021-10-18 1641 ret = ufs->drv_data->post_hce_enable(ufs);
52e5035f7b079be drivers/scsi/ufs/ufs-exynos.c Chanho Park 2021-10-18 1642
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1643 break;
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1644 }
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1645
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1646 return ret;
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1647 }
55f4b1f73631a08 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 1648
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-05-02 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 4:22 [PATCH v3] scsi: ufs: core: call hibern8 notify when hibern8 cmd failed Hongjie Fang
2026-04-30 17:30 ` Bart Van Assche
2026-05-01 12:53 ` Fang Hongjie(方洪杰)
2026-05-02 10:05 ` kernel test robot [this message]
2026-05-02 13:57 ` 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=202605021742.XyNEfM7G-lkp@intel.com \
--to=lkp@intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=hongjiefang@asrmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox