From: "Jérôme Pouiller" <jerome.pouiller@silabs.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Riccardo Ferrazzo <rferrazzo@came.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Kalle Valo <kvalo@codeaurora.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <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 15:04:48 +0100 [thread overview]
Message-ID: <3633390.6h3MoT29mx@pc-42> (raw)
In-Reply-To: <5feac65fc71f4060abb7421ee4571af4@came.com>
Hello Riccardo,
On Friday 18 February 2022 14:53:35 CET Riccardo Ferrazzo wrote:
>
> Signed-off-by: Riccardo Ferrazzo <rferrazzo@came.com>
>
>
> Sorry for the footer it is added automatically
>
Your mail has probably not been received by everyone since you sent it
in html[1] (try also to avoid top-posting).
Nevertheless, Greg, is it sufficient for you?
[1]: https://useplaintext.email/
> On Friday 18 February 2022 12:00:54 CET Greg Kroah-Hartman wrote:
> > 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?
>
> The author hasn't used format-patch to transmit this patch.
>
> Riccardo, can you reply to this mail with the mention "Signed-off-by:
> Your name <your-mail@dom.com>"? It certifies that you wrote it or
> otherwise have the right to pass it on as an open-source patch[1].
>
>
> [1] https://urlsand.esvalabs.com/?u=https%3A%2F%2Fwww.kernel.org%2Fdoc%2Fhtml%2Fv4.17%2Fprocess%2Fsubmitting-patches.html%23sign-your-work-the-developer-s-certificate-of-origin&e=09733f94&h=e09f2efa&f=y&p=n<https://urldefense.com/v3/__https://urlsand.esvalabs.com/?u=https*3A*2F*2Fwww.kernel.org*2Fdoc*2Fhtml*2Fv4.17*2Fprocess*2Fsubmitting-patches.html*23sign-your-work-the-developer-s-certificate-of-origin&e=09733f94&h=e09f2efa&f=y&p=n__;JSUlJSUlJSUl!!N30Cs7Jr!GRgB_JlhZF2XzaDEB1ZDnSbLiMmD8XdrmC_uqyLoczR5e05vvMlDCgyKlEu3XyI3PdJK$>
>
> Thank you,
>
> --
> Jérôme Pouiller
>
>
>
--
Jérôme Pouiller
next prev parent reply other threads:[~2022-02-18 14:05 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
2022-02-18 11:11 ` Jérôme Pouiller
[not found] ` <5feac65fc71f4060abb7421ee4571af4@came.com>
2022-02-18 14:04 ` Jérôme Pouiller [this message]
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=3633390.6h3MoT29mx@pc-42 \
--to=jerome.pouiller@silabs.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).