All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
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: Tue, 21 Mar 2017 13:43:34 +0200	[thread overview]
Message-ID: <87h92mam8p.fsf@purkki.adurom.net> (raw)
In-Reply-To: <be488eab-b822-f99a-a0d2-737e52f5b048@lwfinger.net> (Larry Finger's message of "Mon, 20 Mar 2017 13:47:39 -0500")

Larry Finger <Larry.Finger@lwfinger.net> writes:

> 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?
>
> Something is wrong with my wireless-testing-next tree. I just built
> the mainline 4.11-rc3, and it does not have the problem. I'm now sure
> that the bisection was wrong.
>
> I will need to refresh w-d-n and try again.

Do you mean wireless-drivers-next or wireless-testing? If the latter,
please note that you cannot really bisect anything on wireless-testing
because it's rebased every time. wireless-drivers-next should be safe to
use for bisection because I don't rebase that unless a major disaster
happens, and IIRC that has not yet happened.

(Well, in theory you can bisect wireless-testing but you have to be
_really_ careful how to bisect and make sure that you follow the history
correctly. Definitely not recommended.)

-- 
Kalle Valo

  reply	other threads:[~2017-03-21 11:43 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
2017-03-22 16:08         ` Larry Finger
2017-03-20 18:47     ` Larry Finger
2017-03-21 11:43       ` Kalle Valo [this message]
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=87h92mam8p.fsf@purkki.adurom.net \
    --to=kvalo@codeaurora.org \
    --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 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.