From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] linux-firmware improvements
Date: Fri, 20 Jul 2018 11:15:24 +0000 [thread overview]
Message-ID: <cover.1532085117.git.Martin.Jansa@gmail.com> (raw)
I care only about the 1st commit, the rest is just what I've noticed
while reading the WHENCE file.
Separating other packages might be useful for someone, the catch-all
linux-firmware package is still huge:
160M 1_0.0+gitAUTOINC+d114732723-r0.old/packages-split/linux-firmware
147M 1_0.0+gitAUTOINC+d114732723-r0/packages-split/linux-firmware
The following changes since commit ff0b682b807959521c85716296de7a1d26d7d18f:
systemd-boot: upgrade to 239 (2018-07-18 10:13:30 +0100)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib jansa/firmware
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=jansa/firmware
Martin Jansa (3):
linux-firmware: add ${PN}-cypress-license handling from
meta-raspberrypi
linux-firmware: update LICENSE for bcm43* packages according to WHENCE
file
linux-firmware: add separate packages for all brcm files
.../linux-firmware/linux-firmware_git.bb | 194 ++++++++++++++----
1 file changed, 151 insertions(+), 43 deletions(-)
--
2.17.1
next reply other threads:[~2018-07-20 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 11:15 Martin Jansa [this message]
2018-07-20 11:15 ` [PATCH 1/3] linux-firmware: add ${PN}-cypress-license handling from meta-raspberrypi Martin Jansa
2018-07-20 11:15 ` [PATCH 2/3] linux-firmware: update LICENSE for bcm43* packages according to WHENCE file Martin Jansa
2018-07-20 11:15 ` [PATCH 3/3] linux-firmware: add separate packages for all brcm files Martin Jansa
2018-07-20 11:35 ` ✗ patchtest: failure for linux-firmware improvements Patchwork
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=cover.1532085117.git.Martin.Jansa@gmail.com \
--to=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