Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1625031 > unrolled thread
| Started by | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| First post | 2017-04-18 07:40 +0200 |
| Last post | 2017-04-18 13:20 +0200 |
| Articles | 4 — 2 participants |
Back to article view | Back to linux.kernel
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
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2017-04-18 07:40 +0200 |
| Subject | linux-next: build failure after merge of the staging tree |
| Message-ID | <txu1Q-2go-5@gated-at.bofh.it> |
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.
--
Cheers,
Stephen Rothwell
[toc] | [next] | [standalone]
| From | Greg KH <greg@kroah.com> |
|---|---|
| Date | 2017-04-18 08:00 +0200 |
| Message-ID | <txuld-2nb-15@gated-at.bofh.it> |
| In reply to | #1625031 |
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
[toc] | [prev] | [next] | [standalone]
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2017-04-18 08:30 +0200 |
| Message-ID | <txuOd-2MU-11@gated-at.bofh.it> |
| In reply to | #1625042 |
Hi Greg,
On Tue, 18 Apr 2017 07:54:40 +0200 Greg KH <greg@kroah.com> wrote:
>
> 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?
Well, drivers/staging/media/atomisp/pci/atomisp2/Makefile lists
css2400/isp/kernels/uds/uds_1.0/ia_css_uds.host.o in atomisp-objs.
The above commit deleted
drivers/staging/media/atomisp/pci/atomisp2/css2400/isp/kernels/uds/uds_1.0/ia_css_uds.host.c
--
Cheers,
Stephen Rothwell
[toc] | [prev] | [next] | [standalone]
| From | Greg KH <greg@kroah.com> |
|---|---|
| Date | 2017-04-18 13:20 +0200 |
| Message-ID | <txzkR-5wU-9@gated-at.bofh.it> |
| In reply to | #1625054 |
On Tue, Apr 18, 2017 at 04:26:52PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> On Tue, 18 Apr 2017 07:54:40 +0200 Greg KH <greg@kroah.com> wrote:
> >
> > 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?
>
> Well, drivers/staging/media/atomisp/pci/atomisp2/Makefile lists
> css2400/isp/kernels/uds/uds_1.0/ia_css_uds.host.o in atomisp-objs.
>
> The above commit deleted
> drivers/staging/media/atomisp/pci/atomisp2/css2400/isp/kernels/uds/uds_1.0/ia_css_uds.host.c
{sigh} It was a long last week... My tree had a "stale" .o file laying
around from the previous build, I can reproduce this now, sorry for the
noise. I'll go fix it...
greg k-h
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web