From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the v4l-dvb-next tree
Date: Wed, 3 Jun 2020 10:13:03 +0200 [thread overview]
Message-ID: <20200603101303.1759d782@coco.lan> (raw)
In-Reply-To: <20200603124646.4ce0ca8b@canb.auug.org.au>
Em Wed, 3 Jun 2020 12:46:46 +1000
Hi Stephen,
Stephen Rothwell <sfr@canb.auug.org.au> escreveu:
> Hi all,
>
> After merging the v4l-dvb-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/staging/media/atomisp/pci/atomisp_compat_css20.c: In function 'atomisp_css_isr_thread':
> drivers/staging/media/atomisp/pci/atomisp_compat_css20.c:4196:9: error: 'atomisp_hw_is_isp2401' undeclared (first use in this function)
> 4196 | if (!atomisp_hw_is_isp2401)
> | ^~~~~~~~~~~~~~~~~~~~~
> drivers/staging/media/atomisp/pci/atomisp_compat_css20.c:4196:9: note: each undeclared identifier is reported only once for each function it appears in
>
> Caused by commit
>
> be1fdab273a9 ("media: atomisp: change the detection of ISP2401 at runtime")
>
> interacting with commit
>
> 7ef17aa55fc3 ("media: atomisp: atomisp_compat_css20.c: detect ISP at runtime")
>
> I have used the version of the v4l-dvb-next tree from next-20200602
> for today.
Sorry for that.
The v4l-dvb-next currently contains some atomisp patches that are
waiting for review at linux-media, while v4l-dvb contains the patches
already reviewed, ready for merging.
The PR for v4l-dvb was submitted today.
I forgot to rebase v4l-dvb-next when some of the patches there
were moved to v4l-dvb. Hopefully, it will be OK on tomorrow's
linux-next, as I did the needed rebase.
Thanks,
Mauro
next prev parent reply other threads:[~2020-06-03 8:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 2:46 linux-next: build failure after merge of the v4l-dvb-next tree Stephen Rothwell
2020-06-03 8:13 ` Mauro Carvalho Chehab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-19 23:55 Stephen Rothwell
2021-09-20 0:19 Stephen Rothwell
2021-09-20 7:39 ` Sean Young
2023-10-09 0:08 Stephen Rothwell
2023-10-09 9:25 ` Bryan O'Donoghue
2023-10-09 9:50 ` Hans Verkuil
2024-05-01 0:22 Stephen Rothwell
2024-05-06 0:49 Stephen Rothwell
2024-05-07 11:56 ` Sakari Ailus
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=20200603101303.1759d782@coco.lan \
--to=mchehab@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.