All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Jérôme Pouiller" <jerome.pouiller@silabs.com>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	Kalle Valo <kvalo@codeaurora.org>,
	devel@driverdev.osuosl.org,
	Riccardo Ferrazzo <rferrazzo@came.com>,
	linux-kernel@vger.kernel.org,
	"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH] staging: wfx: fix scan with WFM200 and WW regulation
Date: Fri, 18 Feb 2022 12:00:54 +0100	[thread overview]
Message-ID: <Yg98Zjikg0ncQv8b@kroah.com> (raw)
In-Reply-To: <2535719.D4RZWD7AcY@pc-42>

On Fri, Feb 18, 2022 at 11:57:47AM +0100, Jérôme Pouiller wrote:
> On Friday 18 February 2022 11:53:58 CET Jerome Pouiller wrote:
> > From: Riccardo Ferrazzo <rferrazzo@came.com>
> > 
> > Some variants of the WF200 disallow active scan on channel 12 and 13.
> > For these parts, the channels 12 and 13 are marked IEEE80211_CHAN_NO_IR.
> > 
> > However, the beacon hint procedure was removing the flag
> > IEEE80211_CHAN_NO_IR from channels where a BSS is discovered. This was
> > making subsequent scans to fail because the driver was trying active
> > scans on prohibited channels.
> > 
> > Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
> 
> I forgot to mention I have reviewed on this patch:
> 
> Reviewed-by: Jérôme Pouiller <jerome.pouiller@silabs.com>

Reviwed-by is implied with signed-off-by.

But what happened to the signed-off-by from the author of this change?

thanks,

greg k-h

  reply	other threads:[~2022-02-18 11:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 10:53 [PATCH] staging: wfx: fix scan with WFM200 and WW regulation Jerome Pouiller
2022-02-18 10:57 ` Jérôme Pouiller
2022-02-18 11:00   ` Greg Kroah-Hartman [this message]
2022-02-18 11:11     ` Jérôme Pouiller
     [not found]       ` <5feac65fc71f4060abb7421ee4571af4@came.com>
2022-02-18 14:04         ` Jérôme Pouiller
2022-02-18 15:50           ` Riccardo Ferrazzo

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=Yg98Zjikg0ncQv8b@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=jerome.pouiller@silabs.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rferrazzo@came.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.