From: "Wold, Saul" <saul.wold@intel.com>
To: "richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"Ng, Wei Tee" <wei.tee.ng@intel.com>
Subject: Re: [PATCH v3 0/3] Set linux-firmware to correct license
Date: Thu, 13 Apr 2017 02:24:38 +0000 [thread overview]
Message-ID: <1492050276.4358.256.camel@intel.com> (raw)
In-Reply-To: <1492010715.26846.1.camel@linuxfoundation.org>
On Wed, 2017-04-12 at 16:25 +0100, Richard Purdie wrote:
> On Sun, 2017-04-09 at 18:58 -0700, wei.tee.ng@intel.com wrote:
> >
> > From: "Ng, Wei Tee" <wei.tee.ng@intel.com>
> >
> > This is the revised version to fix the ipk packaging error as
> > below:
> > ERROR: linux-firmware-1_0.0+gitAUTOINC+b14134583c-r0
> > do_package_write_ipk: Function failed: do_package_ipk
> >
> > These patches is to update the SRCREV of linux-firmware to the
> > latest
> > HEAD
> > and set the license file explicitly for linux-firmware-carl9170 to
> > GPL-2.
> > This also targeted to solve the Bugzilla ID 11090.
> >
> > The SRCREV for linux-firmware was updated to the latest in order to
> > include the GPL-2 license file. The netronome firmware was removed
> > until rpm packaging issue is resolved.
> >
> > This configuration are build and tested for ipk, rpm and deb
> > packaging.
> >
> > Please review and provide feedback if you have any.
>
> We can't upgrade this recipe at this point in the release unless
> there
> is a pressing reason to. You don't list any reason at all for the
> upgrade here so I can only assume there isn't one. This patch and the
> ones that depend on it will therefore have to wait for 2.4.
>
Richard,
I would like to advocate that this is similar to the kernel, there are
new firmware packages available for new hardware and if we want to be
supporting leading edge hardware, we need to have the latest versions
of linux-firmware.
This is what I consider a leaf recipe, it does not directly affect
other and is therefore fairly safe to take the latest version.
Please consider this for 2.3, thanks!
Sau!
> Cheers,
>
> Richard
next prev parent reply other threads:[~2017-04-13 2:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 1:58 [PATCH v3 0/3] Set linux-firmware to correct license wei.tee.ng
2017-04-10 1:58 ` [PATCH v3 1/3] linux-firmware: update to revision a4dde74b wei.tee.ng
2017-04-10 1:58 ` [PATCH v3 2/3] linux-firmware: Set the license for carl9170 to GPLv2 wei.tee.ng
2017-04-10 1:58 ` [PATCH v3 3/3] linux-firmware: Fix build failure when update SRCREV to latest HEAD wei.tee.ng
2017-04-12 15:25 ` [PATCH v3 0/3] Set linux-firmware to correct license Richard Purdie
2017-04-13 2:24 ` Wold, Saul [this message]
2017-04-13 22:58 ` Burton, Ross
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=1492050276.4358.256.camel@intel.com \
--to=saul.wold@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=wei.tee.ng@intel.com \
/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.