Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Stanley Chu <stanley.chu@mediatek.com>,
	linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
	avri.altman@wdc.com, alim.akhtar@samsung.com, jejb@linux.ibm.com
Cc: kbuild-all@lists.01.org, beanhuo@micron.com,
	asutoshd@codeaurora.org, cang@codeaurora.org,
	matthias.bgg@gmail.com, bvanassche@acm.org
Subject: Re: [PATCH v3 8/8] scsi: ufs-mediatek: Introduce event_notify implementation
Date: Sat, 5 Dec 2020 05:07:21 +0800	[thread overview]
Message-ID: <202012050556.IkyDt1HQ-lkp@intel.com> (raw)
In-Reply-To: <20201204095007.20639-9-stanley.chu@mediatek.com>

[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]

Hi Stanley,

I love your patch! Perhaps something to improve:

[auto build test WARNING on scsi/for-next]
[also build test WARNING on mkp-scsi/for-next next-20201204]
[cannot apply to v5.10-rc6]
[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]

url:    https://github.com/0day-ci/linux/commits/Stanley-Chu/Refine-error-history-and-introduce-event_notify-vop/20201204-175402
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/6a9665f1084bfc3835aa474e280739cc078f1da2
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Stanley-Chu/Refine-error-history-and-introduce-event_notify-vop/20201204-175402
        git checkout 6a9665f1084bfc3835aa474e280739cc078f1da2
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

   drivers/scsi/ufs/ufs-mediatek.c: In function 'ufs_mtk_event_notify':
>> drivers/scsi/ufs/ufs-mediatek.c:1011:27: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
    1011 |  trace_ufs_mtk_event(evt, (int)data);
         |                           ^

vim +1011 drivers/scsi/ufs/ufs-mediatek.c

  1007	
  1008	static void ufs_mtk_event_notify(struct ufs_hba *hba,
  1009					 enum ufs_event_type evt, void *data)
  1010	{
> 1011		trace_ufs_mtk_event(evt, (int)data);
  1012	}
  1013	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 75529 bytes --]

      reply	other threads:[~2020-12-04 21:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04  9:49 [PATCH v3 0/8] Refine error history and introduce event_notify vop Stanley Chu
2020-12-04  9:50 ` [PATCH v3 1/8] scsi: ufs: Remove unused setup_regulators variant function Stanley Chu
2020-12-04  9:50 ` [PATCH v3 2/8] scsi: ufs: Introduce phy_initialization helper Stanley Chu
2020-12-04  9:50 ` [PATCH v3 3/8] scsi: ufs-cdns: Use " Stanley Chu
2020-12-04  9:50 ` [PATCH v3 4/8] scsi: ufs-dwc: " Stanley Chu
2020-12-04  9:50 ` [PATCH v3 5/8] scsi: ufs: Add error history for abort event in UFS Device W-LUN Stanley Chu
2020-12-04  9:50 ` [PATCH v3 6/8] scsi: ufs: Refine error history functions Stanley Chu
2020-12-04  9:50 ` [PATCH v3 7/8] scsi: ufs: Introduce event_notify variant function Stanley Chu
2020-12-04  9:50 ` [PATCH v3 8/8] scsi: ufs-mediatek: Introduce event_notify implementation Stanley Chu
2020-12-04 21:07   ` kernel test robot [this message]

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=202012050556.IkyDt1HQ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alim.akhtar@samsung.com \
    --cc=asutoshd@codeaurora.org \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=cang@codeaurora.org \
    --cc=jejb@linux.ibm.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=matthias.bgg@gmail.com \
    --cc=stanley.chu@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox