From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] linux-firmware: split into bus specific packages.
Date: Mon, 14 Feb 2011 11:19:07 -0700 [thread overview]
Message-ID: <4D59721B.6060103@mentor.com> (raw)
In-Reply-To: <AANLkTimu=72wQjT_m_ECes1C8rOfPD37trVY1KPkWNAT@mail.gmail.com>
On 02/14/2011 11:10 AM, Filip Zyzniewski wrote:
> On 2/14/11, Phil Blundell<philb@gnu.org> wrote:
>> Yeah, agreed. Or even a split down to individual devices/drivers since
>> each of the Ralink firmware binaries is quite large in itself.
>
> Yeah, I agree it is a good idea, it just isn't needed for us.
>
> So could this be done in two steps:
> 1) this patch (by me) - split into buses;
> 2) second patch (by whoever needs this) - furtherly split bus packages
> by devices?
I think that's fine. See my other email just now and we'll push v2,
assuming I'm remembering how upgrades work, right :)
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-02-14 18:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 14:08 [PATCH] linux-firmware: split into bus specific packages Filip Zyzniewski
2011-02-14 15:58 ` Otavio Salvador
2011-02-14 16:17 ` Eric Bénard
2011-02-14 17:08 ` Filip Zyzniewski
2011-02-14 17:13 ` Otavio Salvador
2011-02-14 17:22 ` Filip Zyzniewski
2011-02-14 17:33 ` Tom Rini
2011-02-14 17:40 ` Phil Blundell
2011-02-14 18:10 ` Filip Zyzniewski
2011-02-14 18:19 ` Tom Rini [this message]
2011-02-14 18:01 ` [PATCHv2] image.bbclass: move insert_feed_uris() to rootfs_ipk.bbclass Filip Zyzniewski
2011-02-14 18:03 ` Filip Zyzniewski
2011-02-14 18:18 ` [PATCH] linux-firmware: split into bus specific packages Tom Rini
2011-02-14 18:46 ` [PATCHv2] " Filip Zyzniewski
2011-02-22 21:15 ` Filip Zyzniewski
2011-02-23 6:33 ` Koen Kooi
2011-02-23 7:12 ` Filip Zyzniewski
2011-02-23 8:52 ` Eric Benard
2011-02-23 13:26 ` Filip Zyzniewski
2011-02-23 14:28 ` Koen Kooi
2011-02-23 7:23 ` Filip Zyzniewski
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=4D59721B.6060103@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@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 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.