public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Sanjay R Mehta <Sanju.Mehta@amd.com>
Cc: kbuild-all@lists.01.org, vkoul@kernel.org,
	dan.j.williams@intel.com, gregkh@linuxfoundation.org,
	Gary.Hook@amd.com, Nehal-bakulchandra.Shah@amd.com,
	Shyam-sundar.S-k@amd.com, davem@davemloft.net,
	mchehab+samsung@kernel.org, robh@kernel.org,
	Jonathan.Cameron@huawei.com, linux-kernel@vger.kernel.org,
	dmaengine@vger.kernel.org, Sanjay R Mehta <sanju.mehta@amd.com>
Subject: Re: [PATCH v2 3/3] dmaengine: ptdma: Add debugfs entries for PTDMA information
Date: Sat, 28 Dec 2019 09:24:11 +0800	[thread overview]
Message-ID: <201912280954.bhIA5CBF%lkp@intel.com> (raw)
In-Reply-To: <1577458112-109734-1-git-send-email-Sanju.Mehta@amd.com>

Hi Sanjay,

I love your patch! Perhaps something to improve:

[auto build test WARNING on linus/master]
[also build test WARNING on v5.5-rc3 next-20191220]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Sanjay-R-Mehta/Add-AMD-PassThru-DMA-Engine-driver/20191227-234539
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 46cf053efec6a3a5f343fead837777efe8252a46
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-129-g341daf20-dirty
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

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


sparse warnings: (new ones prefixed by >>)

>> drivers/dma/ptdma/ptdma-dev.c:139:5: sparse: sparse: symbol 'pt_present' was not declared. Should it be static?
   drivers/dma/ptdma/ptdma-dev.c:169:25: sparse: sparse: cast from restricted __le32
   drivers/dma/ptdma/ptdma-dev.c:169:23: sparse: sparse: incorrect type in assignment (different base types)
   drivers/dma/ptdma/ptdma-dev.c:169:23: sparse:    expected unsigned int [usertype]
   drivers/dma/ptdma/ptdma-dev.c:169:23: sparse:    got restricted __le32 [usertype]
   drivers/dma/ptdma/ptdma-dev.c:199:21: sparse: sparse: incorrect type in assignment (different base types)
   drivers/dma/ptdma/ptdma-dev.c:199:21: sparse:    expected restricted __le32 [addressable] [assigned] [usertype] length
   drivers/dma/ptdma/ptdma-dev.c:199:21: sparse:    got unsigned long long [usertype] src_len
   drivers/dma/ptdma/ptdma-dev.c:201:21: sparse: sparse: incorrect type in assignment (different base types)
   drivers/dma/ptdma/ptdma-dev.c:201:21: sparse:    expected restricted __le32 [addressable] [assigned] [usertype] src_lo
   drivers/dma/ptdma/ptdma-dev.c:201:21: sparse:    got unsigned int [usertype]
   drivers/dma/ptdma/ptdma-dev.c:204:21: sparse: sparse: incorrect type in assignment (different base types)
   drivers/dma/ptdma/ptdma-dev.c:204:21: sparse:    expected restricted __le32 [addressable] [assigned] [usertype] dst_lo
   drivers/dma/ptdma/ptdma-dev.c:204:21: sparse:    got unsigned int [usertype]

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation

  reply	other threads:[~2019-12-28  1:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-27 14:48 [PATCH v2 3/3] dmaengine: ptdma: Add debugfs entries for PTDMA information Sanjay R Mehta
2019-12-28  1:24 ` kbuild test robot [this message]
2019-12-28  1:24 ` [RFC PATCH] dmaengine: ptdma: pt_present() can be static kbuild 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=201912280954.bhIA5CBF%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Gary.Hook@amd.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=Nehal-bakulchandra.Shah@amd.com \
    --cc=Sanju.Mehta@amd.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=dan.j.williams@intel.com \
    --cc=davem@davemloft.net \
    --cc=dmaengine@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=robh@kernel.org \
    --cc=vkoul@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