From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android12-5.4 1/1] drivers/scsi/ufs/ufs-mediatek.c:181:5: sparse: sparse: symbol 'ufs_mtk_wait_link_state' was not declared. Should it be static?
Date: Tue, 27 May 2025 09:32:28 +0800 [thread overview]
Message-ID: <202505270950.Mfklf6q3-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android12-5.4
head: 71d0515397de96c7ff0dd2c6be6e2af7a113e997
commit: 745c7d9dd4c72286ffb21123ea61da4bb36c6a3a [1/1] UPSTREAM: scsi: ufs-mediatek: Do not gate clocks if auto-hibern8 is not entered yet
config: arm64-randconfig-r111-20250527 (https://download.01.org/0day-ci/archive/20250527/202505270950.Mfklf6q3-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 10.5.0
reproduce: (https://download.01.org/0day-ci/archive/20250527/202505270950.Mfklf6q3-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/202505270950.Mfklf6q3-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/scsi/ufs/ufs-mediatek.c:181:5: sparse: sparse: symbol 'ufs_mtk_wait_link_state' was not declared. Should it be static?
vim +/ufs_mtk_wait_link_state +181 drivers/scsi/ufs/ufs-mediatek.c
180
> 181 int ufs_mtk_wait_link_state(struct ufs_hba *hba, u32 state,
182 unsigned long max_wait_ms)
183 {
184 ktime_t timeout, time_checked;
185 u32 val;
186
187 timeout = ktime_add_us(ktime_get(), ms_to_ktime(max_wait_ms));
188 do {
189 time_checked = ktime_get();
190 ufshcd_writel(hba, 0x20, REG_UFS_DEBUG_SEL);
191 val = ufshcd_readl(hba, REG_UFS_PROBE);
192 val = val >> 28;
193
194 if (val == state)
195 return 0;
196
197 /* Sleep for max. 200us */
198 usleep_range(100, 200);
199 } while (ktime_before(time_checked, timeout));
200
201 if (val == state)
202 return 0;
203
204 return -ETIMEDOUT;
205 }
206
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-27 1:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202505270950.Mfklf6q3-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.