From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Vinod Koul <vkoul@kernel•org>
Cc: Qing Wang <wangqing@vivo•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the dmaengine tree
Date: Tue, 26 Oct 2021 16:07:48 +1100 [thread overview]
Message-ID: <20211026160748.67012c44@canb.auug.org.au> (raw)
In-Reply-To: <20211026160657.63ceb380@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 3814 bytes --]
Hi all,
On Tue, 26 Oct 2021 16:06:57 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Hi all,
>
> After merging the dmaengine tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
drivers/message/fusion/mptbase.c: In function 'PrimeIocFifos':
drivers/message/fusion/mptbase.c:4446:35: error: passing argument 1 of 'dma_set_mask_and_coherent' from incompatible pointer type [-Werror=incompatible-pointer-types]
4446 | if (!dma_set_mask_and_coherent(&ioc->pcidev, DMA_BIT_MASK(32))) {
| ^~~~~~~~~~~~
| |
| struct pci_dev **
In file included from include/linux/pci-dma-compat.h:8,
from include/linux/pci.h:2443,
from drivers/message/fusion/mptbase.c:56:
include/linux/dma-mapping.h:442:60: note: expected 'struct device *' but argument is of type 'struct pci_dev **'
442 | static inline int dma_set_mask_and_coherent(struct device *dev, u64 mask)
| ~~~~~~~~~~~~~~~^~~
drivers/message/fusion/mptbase.c:4454:31: error: passing argument 1 of 'dma_set_mask_and_coherent' from incompatible pointer type [-Werror=incompatible-pointer-types]
4454 | dma_set_mask_and_coherent(&ioc->pcidev, DMA_BIT_MASK(64));
| ^~~~~~~~~~~~
| |
| struct pci_dev **
In file included from include/linux/pci-dma-compat.h:8,
from include/linux/pci.h:2443,
from drivers/message/fusion/mptbase.c:56:
include/linux/dma-mapping.h:442:60: note: expected 'struct device *' but argument is of type 'struct pci_dev **'
442 | static inline int dma_set_mask_and_coherent(struct device *dev, u64 mask)
| ~~~~~~~~~~~~~~~^~~
drivers/message/fusion/mptbase.c:4590:33: error: passing argument 1 of 'dma_set_mask_and_coherent' from incompatible pointer type [-Werror=incompatible-pointer-types]
4590 | !dma_set_mask_and_coherent(&ioc->pcidev, ioc->dma_mask))
| ^~~~~~~~~~~~
| |
| struct pci_dev **
In file included from include/linux/pci-dma-compat.h:8,
from include/linux/pci.h:2443,
from drivers/message/fusion/mptbase.c:56:
include/linux/dma-mapping.h:442:60: note: expected 'struct device *' but argument is of type 'struct pci_dev **'
442 | static inline int dma_set_mask_and_coherent(struct device *dev, u64 mask)
| ~~~~~~~~~~~~~~~^~~
drivers/message/fusion/mptbase.c:4614:33: error: passing argument 1 of 'dma_set_mask_and_coherent' from incompatible pointer type [-Werror=incompatible-pointer-types]
4614 | !dma_set_mask_and_coherent(&ioc->pcidev, DMA_BIT_MASK(64)))
| ^~~~~~~~~~~~
| |
| struct pci_dev **
In file included from include/linux/pci-dma-compat.h:8,
from include/linux/pci.h:2443,
from drivers/message/fusion/mptbase.c:56:
include/linux/dma-mapping.h:442:60: note: expected 'struct device *' but argument is of type 'struct pci_dev **'
442 | static inline int dma_set_mask_and_coherent(struct device *dev, u64 mask)
| ~~~~~~~~~~~~~~~^~~
> Caused by commit
>
> 981b43434b28 ("message: fusion: switch from 'pci_' to 'dma_' API")
>
> I have used the dmaengine tree from next-20211025 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-10-26 5:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 5:06 linux-next: build failure after merge of the dmaengine tree Stephen Rothwell
2021-10-26 5:07 ` Stephen Rothwell [this message]
2021-10-26 5:26 ` Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2022-06-10 2:46 Stephen Rothwell
2022-06-10 4:32 ` Vinod Koul
2023-09-29 3:13 Stephen Rothwell
2023-10-02 16:09 ` Vinod Koul
2023-10-10 3:54 Stephen Rothwell
2023-10-10 6:59 ` Vinod Koul
2023-10-11 13:41 ` Rob Herring
2023-10-12 12:30 ` Vinod Koul
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=20211026160748.67012c44@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=vkoul@kernel$(echo .)org \
--cc=wangqing@vivo$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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