From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
"Igor M. Liplianin" <liplianin@me.by>
Subject: Re: [Regression] Build failure in current mainline - firmware related
Date: Sun, 11 Jan 2009 12:42:50 -0200 [thread overview]
Message-ID: <20090111124250.05b6dff4@pedra.chehab.org> (raw)
In-Reply-To: <1231598216.5806.124.camel@macbook.infradead.org>
On Sat, 10 Jan 2009 14:36:56 +0000
David Woodhouse <dwmw2@infradead.org> 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
Sorry for that. It seems that, I've committed Igor patch with a dirty tree. So, one
patch for me to allow out-of-tree compiling were merged with the real patch
from Igor.
--
Cheers,
Mauro
next prev parent reply other threads:[~2009-01-11 14:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 11:47 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 [this message]
2009-01-11 15:01 ` David Woodhouse
2009-01-11 19:07 ` Rafael J. Wysocki
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=20090111124250.05b6dff4@pedra.chehab.org \
--to=mchehab@redhat.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liplianin@me.by \
--cc=rjw@sisk.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®