Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1625042
| From | Greg KH <greg@kroah.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: linux-next: build failure after merge of the staging tree |
| Date | 2017-04-18 08:00 +0200 |
| Message-ID | <txuld-2nb-15@gated-at.bofh.it> (permalink) |
| References | <txu1Q-2go-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Apr 18, 2017 at 03:32:20PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> After merging the staging tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> make[7]: *** No rule to make target 'drivers/staging/media/atomisp/pci/atomisp2/css2400/isp/kernels/uds/uds_1.0/ia_css_uds.host.o', needed by 'drivers/staging/media/atomisp/pci/atomisp2/atomisp.o'. Stop.
>
> Caused by commit
>
> 7afe8f84f793 ("atomisp: remove UDS kernel code")
>
> I have used the staging tree from next-20170413 for today.
Ok, the 0-day bot reported something odd like this, with Alan's original
patches, but I couldn't reproduce it, and then when I applied them, the
0-day bot worked just fine. But now you are having the same issue.
I'm totally confused, Alan, any ideas?
thanks,
greg k-h
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
linux-next: build failure after merge of the staging tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-04-18 07:40 +0200
Re: linux-next: build failure after merge of the staging tree Greg KH <greg@kroah.com> - 2017-04-18 08:00 +0200
Re: linux-next: build failure after merge of the staging tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-04-18 08:30 +0200
Re: linux-next: build failure after merge of the staging tree Greg KH <greg@kroah.com> - 2017-04-18 13:20 +0200
csiph-web