Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] package/wireless-regdb: bump version to 2020.11.20
Date: Sun, 22 Nov 2020 16:33:01 +0100	[thread overview]
Message-ID: <20201122163301.190f8b0b@gmx.net> (raw)
In-Reply-To: <87a6v9wjn7.fsf@dell.be.48ers.dk>

Hello Peter,

On Sun, 22 Nov 2020 15:28:28 +0100, Peter Korsgaard <peter@korsgaard.com> wrote:

> >>>>> "Peter" == Peter Seiderer <ps.report@gmx.net> writes:
>
>  > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>
> You didn't mark this for next. Is there a specific reason why this
> should be applied to master?
>

At your choice ;-) (I was too undecided if a up-to-date wireless-regdb is
important enough/accounts as bug fix or is stuff for next, but tending more
to the up-to-date case...)

Regards,
Peter


Short commit log taken from [1]:

wireless-regdb: update regulatory database based on preceding
wireless-regdb: Update regulatory rules for Kazakhstan (KZ)
wireless-regdb: update 5.8 GHz regulatory rule for GB	Seth Forshee
wireless-regdb: Update regulatory rules for Pakistan (PK) on 5GHz
wireless-regdb: Update regulatory rules for Croatia (HR)
wireless-regdb: restore channel 12 & 13 limitation in the US
wireless-regdb: update regulatory rules for Egypt (EG)

[1] https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/log/

  reply	other threads:[~2020-11-22 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 19:41 [Buildroot] [PATCH v1] package/wireless-regdb: bump version to 2020.11.20 Peter Seiderer
2020-11-22 14:28 ` Peter Korsgaard
2020-11-22 15:33   ` Peter Seiderer [this message]
2020-11-22 15:57     ` Peter Korsgaard
2020-12-11 10:24 ` Peter Korsgaard

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=20201122163301.190f8b0b@gmx.net \
    --to=ps.report@gmx.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox