From: Diederik de Haas <didi.debian@cknow.org>
To: "Bonaccorso, Salvatore" <carnil@debian.org>,
"Kumar, M Chetan" <m.chetan.kumar@intel.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linuxwwan <linuxwwan@intel.com>,
"loic.poulain@linaro.org" <loic.poulain@linaro.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"ryazanov.s.a@gmail.com" <ryazanov.s.a@gmail.com>
Subject: Re: drivers/net/wwan/iosm/iosm_ipc_protocol.c:244:36: error: passing argument 3 of 'dma_alloc_coherent' from incompatible pointer type [-Werror=incompatible-pointer-types]
Date: Tue, 22 Nov 2022 12:19:48 +0100 [thread overview]
Message-ID: <2659493.mvXUDI8C0e@bagend> (raw)
In-Reply-To: <3150689.e9J7NaK4W3@bagend>
[-- Attachment #1: Type: text/plain, Size: 452 bytes --]
The procedure missed an important step, added below:
On Monday, 21 November 2022 15:16:52 CET Diederik de Haas wrote:
> # Clean things up and do the actual build
> $ dpkg-architecture -c fakeroot debian/rules maintainerclean
> $ dpkg-architecture -c debian/rules orig
$ dpkg-architecture -c debian/rules debian/control
> $ time dpkg-architecture -c fakeroot debian/rules binary-indep
> $ time dpkg-architecture -c fakeroot debian/rules binary-arch
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2022-11-22 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 19:25 drivers/net/wwan/iosm/iosm_ipc_protocol.c:244:36: error: passing argument 3 of 'dma_alloc_coherent' from incompatible pointer type [-Werror=incompatible-pointer-types] Salvatore Bonaccorso
2022-11-21 13:36 ` Diederik de Haas
2022-11-21 13:47 ` Kumar, M Chetan
2022-11-21 14:16 ` Diederik de Haas
2022-11-22 11:19 ` Diederik de Haas [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=2659493.mvXUDI8C0e@bagend \
--to=didi.debian@cknow.org \
--cc=carnil@debian.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxwwan@intel.com \
--cc=loic.poulain@linaro.org \
--cc=m.chetan.kumar@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ryazanov.s.a@gmail.com \
/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.