From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit branch/2018.05.x] package/wireless-regdb: bump version to 2018.05.31
Date: Mon, 23 Jul 2018 14:28:32 +0200 [thread overview]
Message-ID: <20180723142832.379d74fb@windsurf> (raw)
In-Reply-To: <20180720221609.BE06A8A295@busybox.osuosl.org>
Hello,
On Sat, 21 Jul 2018 00:20:58 +0200, Peter Korsgaard wrote:
> commit: https://git.buildroot.net/buildroot/commit/?id=eece13dcecdfc9dd283c068ec64000edb5fb09e4
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/2018.05.x
>
> Added license hash, updated project URL, old site is dead.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> (cherry picked from commit 54917abdd74158298fd848a58117c796c641a130)
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
I'm wondering why you backported this change. Indeed, the backport of
"wireless-regdb: add regulatory.db[.p7s] to /lib/firmware" broke the
build of wireless-regdb on 2018.05.x, but perhaps the right thing to do
was to revert rather than bump wireless-regdb ?
In any case, the 2018.05.1 currently has a broken wireless-regdb
package because of this: your backport of the wireless-regdb bump has
been done after the 2018.05.1 tag.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-07-23 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 22:20 [Buildroot] [git commit branch/2018.05.x] package/wireless-regdb: bump version to 2018.05.31 Peter Korsgaard
2018-07-23 12:28 ` Thomas Petazzoni [this message]
2018-08-23 15:32 ` Peter Korsgaard
2018-08-23 16:30 ` Raphael Jacob
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=20180723142832.379d74fb@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.