Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Cristian <caravena@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Date: Tue, 28 Nov 2017 13:21:54 +0100	[thread overview]
Message-ID: <1511871714.7841.0.camel@sipsolutions.net> (raw)
In-Reply-To: <CABwnbUmWhxx0oN8H1H-0Qy9OYczszFX7yoLLud7VSBLxTn7Dyg@mail.gmail.com> (sfid-20171128_130918_213277_F9199602)

On Tue, 2017-11-28 at 09:09 -0300, Cristian wrote:
> Hello,
> 
> Linux version 4.15.0-041500rc1-generic
> 
> Report in:
> https://bugzilla.kernel.org/show_bug.cgi?id=198013
> 
> dmesg:
> [    5.663292] platform regulatory.0: Direct firmware load for
> regulatory.db failed with error -2

Yeah, nothing to worry about.

Seth will publish the file, and then people can get it, but until then
it's not actually needed.

johannes

      reply	other threads:[~2017-11-28 12:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 12:09 platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 Cristian
2017-11-28 12:21 ` Johannes Berg [this message]

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=1511871714.7841.0.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=caravena@gmail.com \
    --cc=linux-wireless@vger.kernel.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