From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Bingbu Cao <bingbu.cao@intel.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the v4l-dvb-next tree
Date: Wed, 1 May 2024 10:22:36 +1000 [thread overview]
Message-ID: <20240501102236.3b2585d1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
Hi all,
After merging the v4l-dvb-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/media/pci/intel/ipu6/ipu6.c: In function 'request_cpd_fw':
drivers/media/pci/intel/ipu6/ipu6.c:529:21: error: implicit declaration of function 'vmalloc'; did you mean 'kvmalloc'? [-Werror=implicit-function-declaration]
529 | dst->data = vmalloc(fw->size);
| ^~~~~~~
| kvmalloc
drivers/media/pci/intel/ipu6/ipu6.c:529:19: error: assignment to 'const u8 *' {aka 'const unsigned char *'} from 'int' makes pointer from integer without a cast [-Werror=int-conversion]
529 | dst->data = vmalloc(fw->size);
| ^
cc1: all warnings being treated as errors
Caused by commit
25fedc021985 ("media: intel/ipu6: add Intel IPU6 PCI device driver")
I have used the vl4-dvb-next tree from next-20240430 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-05-01 0:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 0:22 Stephen Rothwell [this message]
2024-05-02 6:15 ` [PATCH 1/1] media: ipu6: Fix vmalloc memory allocation Sakari Ailus
2024-05-02 10:03 ` Mauro Carvalho Chehab
2024-05-02 15:49 ` [PATCH 1/1] media: intel/ipu6: Don't re-allocate memory for firmware Sakari Ailus
-- strict thread matches above, loose matches on Subject: below --
2024-05-06 0:49 linux-next: build failure after merge of the v4l-dvb-next tree Stephen Rothwell
2024-05-07 11:56 ` Sakari Ailus
2023-10-09 0:08 Stephen Rothwell
2023-10-09 9:25 ` Bryan O'Donoghue
2023-10-09 9:50 ` Hans Verkuil
2021-09-20 0:19 Stephen Rothwell
2021-09-20 7:39 ` Sean Young
2021-05-19 23:55 Stephen Rothwell
2020-06-03 2:46 Stephen Rothwell
2020-06-03 8:13 ` Mauro Carvalho Chehab
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=20240501102236.3b2585d1@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bingbu.cao@intel.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).