Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: Christoph Hellwig <hch@lst.de>
Cc: kbuild test robot <fengguang.wu@intel.com>,
	kbuild-all@01.org, linux-scsi@vger.kernel.org,
	sparclinux@vger.kernel.org
Subject: Re: [hch-scsi-queue:drivers-for-3.19 174/180] drivers/scsi/wd719x.c:247:2: error: implicit declaration of function 'dma_cache_sync'
Date: Wed, 26 Nov 2014 18:32:48 +0100	[thread overview]
Message-ID: <201411261832.48201.linux@rainbow-software.org> (raw)
In-Reply-To: <20141126102843.GB23189@lst.de>

On Wednesday 26 November 2014 11:28:43 Christoph Hellwig wrote:
> Hi sparc folks,
>
> any idea where the build error below comes from?  This new driver pulls
> in <linux/dma-mapping.h>, but still doesn't seem to get a prototype for
> dma_cache_sync on sparc64.

wd819x should probably depend on VIRT_TO_BUS? But that means it will not work 
on sparc. Is there a way to make it work? I have a sparc machine but haven't 
tested it.

> On Tue, Nov 25, 2014 at 11:42:38PM +0800, kbuild test robot wrote:
> > tree:   git://git.infradead.org/users/hch/scsi-queue.git drivers-for-3.19
> > head:   38d5c8336e60bf6e53a1da9586befe82fa75171b
> > commit: 48a31030066315a74e6c11153b4382edbf133bb3 [174/180] wd719x:
> > Introduce Western Digital WD7193/7197/7296 PCI SCSI card driver config:
> > sparc64-allyesconfig (attached as .config)
> > reproduce:
> >   wget
> > https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin
> >/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
> >   git checkout 48a31030066315a74e6c11153b4382edbf133bb3
> >   # save the attached .config to linux build tree
> >   make.cross ARCH=sparc64
> >
> > All error/warnings:
> >
> >    drivers/scsi/wd719x.c: In function 'wd719x_queuecommand':
> > >> drivers/scsi/wd719x.c:247:2: error: implicit declaration of function
> > >> 'dma_cache_sync' [-Werror=implicit-function-declaration]
> >
> >      dma_cache_sync(&wd->pdev->dev, cmd->sense_buffer,
> >      ^
> >    cc1: some warnings being treated as errors
> >
> > vim +/dma_cache_sync +247 drivers/scsi/wd719x.c
> >
> >    241		memcpy(scb->CDB, cmd->cmnd, cmd->cmd_len);
> >    242
> >    243		/* map sense buffer */
> >    244		scb->sense_buf_length = SCSI_SENSE_BUFFERSIZE;
> >    245		cmd->SCp.dma_handle = dma_map_single(&wd->pdev->dev,
> > cmd->sense_buffer, 246				SCSI_SENSE_BUFFERSIZE, DMA_FROM_DEVICE);
> >
> >  > 247		dma_cache_sync(&wd->pdev->dev, cmd->sense_buffer,
> >
> >    248				SCSI_SENSE_BUFFERSIZE, DMA_FROM_DEVICE);
> >    249		scb->sense_buf = cpu_to_le32(cmd->SCp.dma_handle);
> >    250
> >


-- 
Ondrej Zary

  reply	other threads:[~2014-11-26 17:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201411252333.lLEJOiQu%fengguang.wu@intel.com>
2014-11-26 10:28 ` [hch-scsi-queue:drivers-for-3.19 174/180] drivers/scsi/wd719x.c:247:2: error: implicit declaration of function 'dma_cache_sync' Christoph Hellwig
2014-11-26 17:32   ` Ondrej Zary [this message]
2014-11-26 19:13     ` Christoph Hellwig
2014-11-26 20:28       ` David Miller

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=201411261832.48201.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=fengguang.wu@intel.com \
    --cc=hch@lst.de \
    --cc=kbuild-all@01.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sparclinux@vger.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