From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
Patches,
the oe-core layer <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] linux-firmware: make the main package depend on all sub-packages
Date: Sat, 06 Apr 2013 12:44:09 +0100 [thread overview]
Message-ID: <1365248649.6526.202.camel@ted> (raw)
In-Reply-To: <CA+chaQfjyRzcCewTaro50-0aSFxNts51m9jUcZPZrdfm-gDHUw@mail.gmail.com>
On Sat, 2013-04-06 at 12:36 +0200, Martin Jansa wrote:
> And also staging firmware files just once to resolve
>
> > WARNING: The recipe linux-firmware is trying to install files into a
> shared area when those files already exist. Those files are:
>
> when building linux-firmware after kernel was built and vice-versa.
What is the point in staging firmware files at all? There is probably a
small space/performance gain to be had there...
Cheers,
Richard
prev parent reply other threads:[~2013-04-06 12:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 17:06 [PATCH] linux-firmware: make the main package depend on all sub-packages Ross Burton
2013-04-05 20:11 ` Otavio Salvador
2013-04-06 10:26 ` Koen Kooi
2013-04-06 10:36 ` Martin Jansa
2013-04-06 11:44 ` Richard Purdie [this message]
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=1365248649.6526.202.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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