On Wed, Apr 06, 2016 at 02:30:41AM +0100, Theodor Gherzan wrote:
> I will have a look.
>

No need to take a look on this anymore Theodor. It was fixed in master.

> Theodor Gherzan
>
> On Tue, Mar 29, 2016 at 11:06 PM, Andrei Gherzan <and...@gherzan.ro> wrote:
> > On Fri, Mar 25, 2016 at 11:34:21AM +1100, Jonathan Liu wrote:
> >> Hi Theodor,
> >>
> >> On 10 March 2016 at 01:15, Theodor Gherzan <theo...@gherzan.ro> wrote:
> >> > From: Theodor Gherzan <theo...@resin.io>
> >> >
> >> > Signed-off-by: Theodor Gherzan <theo...@resin.io>
> >> > ---
> >> >  .../linux-firmware/LICENSE.broadcom_brcm80211      | 205 
> >> > +++++++++++++++++++++
> >> >  .../linux-firmware/brcmfmac43430-sdio.bin          | Bin 0 -> 368957 
> >> > bytes
> >> >  .../linux-firmware/brcmfmac43430-sdio.txt          |  66 +++++++
> >> >  .../linux-firmware/linux-firmware_git.bbappend     |  29 +++
> >> >  4 files changed, 300 insertions(+)
> >> >  create mode 100644 
> >> > recipes-kernel/linux-firmware/linux-firmware/LICENSE.broadcom_brcm80211
> >> >  create mode 100644 
> >> > recipes-kernel/linux-firmware/linux-firmware/brcmfmac43430-sdio.bin
> >> >  create mode 100644 
> >> > recipes-kernel/linux-firmware/linux-firmware/brcmfmac43430-sdio.txt
> >> >  create mode 100644 
> >> > recipes-kernel/linux-firmware/linux-firmware_git.bbappend
> >>
> >> I get the following warning when building an image that installs
> >> linux-firmware-ralink package (but not any of the other firmware
> >> packages):
> >> [log_check] WARNING: The license listed Firmware-broadcom_brcm80211
> >> was not in the licenses collected for recipe linux-firmware
> >>
> >> It seems the license is not being packaged correctly.
> >>
> >> Could you please have a look?
> >
> > Theodor,
> >
> > Any chance you can take a look on this?
> >
> > Cheers!
> >
> > --
> > Andrei Gherzan

--
Andrei Gherzan

Attachment: signature.asc
Description: PGP signature

-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to