From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>,
Xose Vazquez Perez <xose.vazquez@gmail.com>
Subject: Re: [BUG] with a 4.10.x kernel it's impossible to apply country regulatory rules
Date: Wed, 22 Mar 2017 16:15:26 +0100 [thread overview]
Message-ID: <20170322151525.GA12702@redhat.com> (raw)
In-Reply-To: <45449c16-5a51-5cec-3254-6f3ce0b71b8a@lwfinger.net>
On Sat, Mar 18, 2017 at 04:30:04PM -0500, Larry Finger wrote:
> On 03/18/2017 02:45 PM, Johannes Berg wrote:
> >On Sat, 2017-03-18 at 12:41 -0500, Larry Finger wrote:
> >>
> >>I have duplicated your bug and I have bisected it to
> >>
> >>commit 2ae0f17df1cd52aafd1ab0415ea1f1dd56dc0e2a
> >>Author: Johannes Berg <johannes.berg@intel.com>
> >>Date: Mon Oct 24 14:40:04 2016 +0200
> >>
> >> genetlink: use idr to track families
> >>
> >>This patch is quite extensive and I have no idea which part is
> >>failing, thus all I can do is report this confirmation.
> >
> >I don't think that makes any sense - have you verified that reverting
> >that makes it go away?
>
> Due to conflicts, I cannot simply revert it; however if I check out
> the previous commit 489111e5c25b93be80340c3113d71903d7c82136
> ("genetlink: statically initialize families"), then the kernel is
> OK.
I just posted a patch which most likely fixes this problem. I have some
other issue on my setup, but seems this issue is also caused by the
same bug in 2ae0f17df1cd52aafd1ab0415ea1f1dd56dc0e2a.
Stanislaw
next prev parent reply other threads:[~2017-03-22 15:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 1:14 [BUG] with a 4.10.x kernel it's impossible to apply country regulatory rules Xose Vazquez Perez
2017-03-18 17:41 ` Larry Finger
2017-03-18 19:45 ` Johannes Berg
2017-03-18 21:30 ` Larry Finger
2017-03-22 15:15 ` Stanislaw Gruszka [this message]
2017-03-22 16:08 ` Larry Finger
2017-03-20 18:47 ` Larry Finger
2017-03-21 11:43 ` Kalle Valo
2017-03-21 13:47 ` Larry Finger
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=20170322151525.GA12702@redhat.com \
--to=sgruszka@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=xose.vazquez@gmail.com \
/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