All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH RFC v4 2/2] dmaengine: avalon-test: Intel Avalon-MM DMA Interface for PCIe test
Date: Sun, 03 Nov 2019 22:58:12 +0800	[thread overview]
Message-ID: <201911032231.xObk3mCa%lkp@intel.com> (raw)
In-Reply-To: <cea86875039d0f58e5c0b19222e4e99fcb9890ea.1572441900.git.a.gordeev.box@gmail.com>

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

Hi Alexander,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on linus/master]
[also build test WARNING on v5.4-rc5]
[cannot apply to next-20191031]
[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/Alexander-Gordeev/dmaengine-avalon-Intel-Avalon-MM-DMA-Interface-for-PCIe/20191102-044059
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 0dbe6cb8f7e05bc9611602ef45980a6c57b245a3
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-6-g57f8611-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/avalon-test/avalon-dev.c:42:30: sparse: sparse: symbol 'avalon_dev_fops' was not declared. Should it be static?
--
>> drivers/dma/avalon-test/avalon-ioctl.c:23:34: sparse: sparse: duplicate [noderef]
>> drivers/dma/avalon-test/avalon-ioctl.c:23:34: sparse: sparse: multiple address space given: <asn:1> & <asn:1>
   drivers/dma/avalon-test/avalon-ioctl.c:23:57: sparse: sparse: multiple address space given: <asn:1> & <asn:1>
--
>> drivers/dma/avalon-test/avalon-xfer.c:52:35: sparse: sparse: mixing different enum types:
>> drivers/dma/avalon-test/avalon-xfer.c:52:35: sparse:    unsigned int enum dma_data_direction
>> drivers/dma/avalon-test/avalon-xfer.c:52:35: sparse:    unsigned int enum dma_transfer_direction
   drivers/dma/avalon-test/avalon-xfer.c:92:65: sparse: sparse: mixing different enum types:
   drivers/dma/avalon-test/avalon-xfer.c:92:65: sparse:    unsigned int enum dma_data_direction
   drivers/dma/avalon-test/avalon-xfer.c:92:65: sparse:    unsigned int enum dma_transfer_direction
   drivers/dma/avalon-test/avalon-xfer.c:117:56: sparse: sparse: mixing different enum types:
   drivers/dma/avalon-test/avalon-xfer.c:117:56: sparse:    unsigned int enum dma_data_direction
   drivers/dma/avalon-test/avalon-xfer.c:117:56: sparse:    unsigned int enum dma_transfer_direction

Please review and possibly fold the followup patch.

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

      parent reply	other threads:[~2019-11-03 14:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30 13:32 [PATCH v4 0/2] dmaengine: avalon: Intel Avalon-MM DMA Interface for PCIe Alexander Gordeev
2019-10-30 13:32 ` [PATCH v4 1/2] " Alexander Gordeev
2019-11-01 23:05   ` kbuild test robot
2019-11-01 23:05     ` kbuild test robot
2019-11-03 14:34   ` kbuild test robot
2019-11-03 14:34     ` kbuild test robot
2019-10-30 13:32 ` [PATCH RFC v4 2/2] dmaengine: avalon-test: Intel Avalon-MM DMA Interface for PCIe test Alexander Gordeev
2019-11-01 21:27   ` kbuild test robot
2019-11-01 22:01   ` kbuild test robot
2019-11-03 14:58   ` [RFC PATCH] dmaengine: avalon-test: avalon_dev_fops can be static kbuild test robot
2019-11-03 14:58   ` kbuild 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=201911032231.xObk3mCa%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.