From: kbuild test robot <lkp@intel.com>
To: Michal Potomski <michalx.potomski@intel.com>
Cc: kbuild-all@01.org, linux-scsi@vger.kernel.org,
vinholikatti@gmail.com, martin.petersen@oracle.com,
jejb@linux.vnet.ibm.com, subhashj@codeaurora.org,
szymonx.mielczarek@intel.com
Subject: Re: [PATCH] scsi: ufs: Fix Runtime PM
Date: Fri, 10 Nov 2017 20:57:55 +0800 [thread overview]
Message-ID: <201711102011.0GhtPssD%fengguang.wu@intel.com> (raw)
In-Reply-To: <20171109091633.2433-1-michalx.potomski@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2217 bytes --]
Hi Michał,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on scsi/for-next]
[also build test ERROR on v4.14-rc8 next-20171109]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Michal-Potomski/scsi-ufs-Fix-Runtime-PM/20171110-191314
base: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
config: m68k-allyesconfig (attached as .config)
compiler: m68k-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=m68k
All errors (new ones prefixed by >>):
drivers/scsi/ufs/ufshcd.c: In function 'ufshcd_pm_runtime_get':
>> drivers/scsi/ufs/ufshcd.c:246:16: error: 'struct dev_pm_info' has no member named 'runtime_status'
if (dev->power.runtime_status == RPM_RESUMING ||
^
drivers/scsi/ufs/ufshcd.c:247:16: error: 'struct dev_pm_info' has no member named 'runtime_status'
dev->power.runtime_status == RPM_SUSPENDING)
^
drivers/scsi/ufs/ufshcd.c: In function 'ufshcd_pm_runtime_put':
drivers/scsi/ufs/ufshcd.c:258:16: error: 'struct dev_pm_info' has no member named 'runtime_status'
if (dev->power.runtime_status == RPM_RESUMING ||
^
drivers/scsi/ufs/ufshcd.c:259:16: error: 'struct dev_pm_info' has no member named 'runtime_status'
dev->power.runtime_status == RPM_SUSPENDING)
^
vim +246 drivers/scsi/ufs/ufshcd.c
242
243 static void ufshcd_pm_runtime_get(struct device *dev)
244 {
245 // Don't trigger PM events while in transition states
> 246 if (dev->power.runtime_status == RPM_RESUMING ||
247 dev->power.runtime_status == RPM_SUSPENDING)
248 pm_runtime_get_noresume(dev);
249 else
250 pm_runtime_get_sync(dev);
251 }
252
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 44359 bytes --]
next prev parent reply other threads:[~2017-11-10 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 9:16 [PATCH] scsi: ufs: Fix Runtime PM Michal Potomski
2017-11-10 12:57 ` kbuild test robot [this message]
2017-11-10 16:38 ` kbuild test robot
2017-11-13 8:47 ` Avri Altman
-- strict thread matches above, loose matches on Subject: below --
2017-11-13 9:14 Michal Potomski
2017-11-21 19:45 ` Subhash Jadavani
2017-11-22 10:06 ` Potomski, MichalX
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=201711102011.0GhtPssD%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michalx.potomski@intel.com \
--cc=subhashj@codeaurora.org \
--cc=szymonx.mielczarek@intel.com \
--cc=vinholikatti@gmail.com \
/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.