lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Fri, 18 Feb 2022 12:11:48 +0100
From:   Jérôme Pouiller <jerome.pouiller@...abs.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        Kalle Valo <kvalo@...eaurora.org>, devel@...verdev.osuosl.org,
        Riccardo Ferrazzo <rferrazzo@...e.com>,
        linux-kernel@...r.kernel.org,
        "David S . Miller" <davem@...emloft.net>
Subject: Re: [PATCH] staging: wfx: fix scan with WFM200 and WW regulation

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@...e.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@...abs.com>
> >
> > I forgot to mention I have reviewed on this patch:
> >
> > Reviewed-by: Jérôme Pouiller <jerome.pouiller@...abs.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@....com>"? It certifies that you wrote it or
otherwise have the right to pass it on as an open-source patch[1].


[1] https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin

Thank you,

-- 
Jérôme Pouiller


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ