From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>,
"Igor M. Liplianin" <liplianin@me.by>,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: [Regression] Build failure in current mainline - firmware related
Date: Sun, 11 Jan 2009 20:07:54 +0100 [thread overview]
Message-ID: <200901112007.55178.rjw@sisk.pl> (raw)
In-Reply-To: <1231598216.5806.124.camel@macbook.infradead.org>
On Saturday 10 January 2009, David Woodhouse wrote:
> On Sun, 2009-01-04 at 22:44 +0100, Sam Ravnborg wrote:
> >
> > We could try to rearrange things so we do not trigger
> > the rebuild of ihex2fw in the modules_install case.
> > This would likely involve creating a new file listing
> > all the firmawre files and share it between firmware/Makefile
> > and scripts/Makefile.fwinst
>
> Didn't we already have that, but it got broken for some reason, by
> unwanted changes in commit 4b29631db33292d416dc395c56122ea865e7635c
>
> Your patch seems to have broken the Fedora kernel build for 'noarch',
> which runs 'make firmware_install' without building a kernel.
>
> Rafael, if you revert Sam's fix and also revert 4b29631d, does it work
> again?
Deosn't revert, sorry.
Can you send me a standalone fix patch to test, please?
Rafael
next prev parent reply other threads:[~2009-01-11 19:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 11:47 [Regression] Build failure in current mainline - firmware related Rafael J. Wysocki
2009-01-03 20:49 ` Sam Ravnborg
2009-01-03 20:54 ` Sam Ravnborg
2009-01-03 21:43 ` Rafael J. Wysocki
2009-01-03 22:14 ` Sam Ravnborg
2009-01-04 21:44 ` Sam Ravnborg
2009-01-04 22:43 ` Rafael J. Wysocki
2009-01-10 14:36 ` David Woodhouse
2009-01-10 14:58 ` David Woodhouse
2009-01-11 14:42 ` Mauro Carvalho Chehab
2009-01-11 15:01 ` David Woodhouse
2009-01-11 19:07 ` Rafael J. Wysocki [this message]
2009-01-08 7:59 ` Sam Ravnborg
2009-01-08 20:17 ` Rafael J. Wysocki
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=200901112007.55178.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liplianin@me.by \
--cc=mchehab@redhat.com \
--cc=sam@ravnborg.org \
/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.