DMA Engine development
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: kbuild-all@01.org, dmaengine@vger.kernel.org, vkoul@kernel.org,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: dma: axi-dmac: Split too large segments
Date: Sat, 16 Feb 2019 18:08:49 +0800	[thread overview]
Message-ID: <201902161857.wzm7oF5T%fengguang.wu@intel.com> (raw)

Hi Lars-Peter,

I love your patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v5.0-rc4 next-20190215]
[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/Alexandru-Ardelean/dma-axi-dmac-Split-too-large-segments/20190216-160002
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 8.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
        GCC_VERSION=8.2.0 make.cross ARCH=xtensa 

All errors (new ones prefixed by >>):

   drivers/dma/dma-axi-dmac.c: In function 'axi_dmac_prep_slave_sg':
>> drivers/dma/dma-axi-dmac.c:443:12: error: implicit declaration of function 'sg_nents_for_dma'; did you mean 'sg_nents_for_len'? [-Werror=implicit-function-declaration]
     num_sgs = sg_nents_for_dma(sgl, sg_len, chan->max_length);
               ^~~~~~~~~~~~~~~~
               sg_nents_for_len
   cc1: some warnings being treated as errors

vim +443 drivers/dma/dma-axi-dmac.c

   427	
   428	static struct dma_async_tx_descriptor *axi_dmac_prep_slave_sg(
   429		struct dma_chan *c, struct scatterlist *sgl,
   430		unsigned int sg_len, enum dma_transfer_direction direction,
   431		unsigned long flags, void *context)
   432	{
   433		struct axi_dmac_chan *chan = to_axi_dmac_chan(c);
   434		struct axi_dmac_desc *desc;
   435		struct axi_dmac_sg *dsg;
   436		struct scatterlist *sg;
   437		unsigned int num_sgs;
   438		unsigned int i;
   439	
   440		if (direction != chan->direction)
   441			return NULL;
   442	
 > 443		num_sgs = sg_nents_for_dma(sgl, sg_len, chan->max_length);
   444		desc = axi_dmac_alloc_desc(num_sgs);
   445		if (!desc)
   446			return NULL;
   447	
   448		dsg = desc->sg;
   449	
   450		for_each_sg(sgl, sg, sg_len, i) {
   451			if (!axi_dmac_check_addr(chan, sg_dma_address(sg)) ||
   452			    !axi_dmac_check_len(chan, sg_dma_len(sg))) {
   453				kfree(desc);
   454				return NULL;
   455			}
   456	
   457			dsg = axi_dmac_fill_linear_sg(chan, direction, sg_dma_address(sg), 1,
   458				sg_dma_len(sg), dsg);
   459		}
   460	
   461		desc->cyclic = false;
   462	
   463		return vchan_tx_prep(&chan->vchan, &desc->vdesc, flags);
   464	}
   465
---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

             reply	other threads:[~2019-02-16 10:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-16 10:08 kbuild test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-25  6:56 dma: axi-dmac: Split too large segments Vinod Koul
2019-02-18  7:34 Lars-Peter Clausen
2019-02-18  7:28 Ardelean, Alexandru
2019-02-15 11:06 Alexandru Ardelean

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=201902161857.wzm7oF5T%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=alexandru.ardelean@analog.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=kbuild-all@01.org \
    --cc=lars@metafoo.de \
    --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