DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=google.com; s=beta;
        h=mime-version:from:date:message-id:subject:to:cc:content-type;
        b=nlbougCrs0FKhLBXCvCGEukfSv6uStYezeH2eZiBPevhCQWmaXDxXkY38L4W0s+mLv
         8NDlB8X3l20d4/7K1OXQ==
MIME-Version: 1.0
From: Mike Waychison <mikew@google.com>
Date: Mon, 2 May 2011 11:57:35 -0700
Message-ID: <BANLkTimmr=rD84cAkQ2xGsG7PccxQKKqVg@mail.gmail.com>
Subject: linux-firmware tree
To: david.woodhouse@intel.com
Cc: linux-kernel@vger.kernel.org
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 819
Lines: 23

Hi David,

I'm trying to understand the purpose of the linux-firmware tree.
Forgive me if this is a stupid question, but the only information
about it I could find was your original post back in 2008:
https://lwn.net/Articles/294308/

Will the Linux kernel sources always continue to have the firmware
blobs and the linux-firmware tree is only for those users of distros
that strip the firmware out?

I'm trying to understand if there would ever be a need to integrate
the linux-firmware tree into our builds (we build a derivative of
Linus' tree).

Thanks,

Mike Waychison
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/