From: Kalle Valo <kvalo@codeaurora.org>
To: Andrew Zaborowski <andrew.zaborowski@intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v6 1/3] cfg80211: Accept multiple RSSI thresholds for CQM
Date: Tue, 21 Feb 2017 10:48:13 +0200 [thread overview]
Message-ID: <87d1ecdj5e.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAOq732LwAs6bG5dPMuBWA7MnSMLSRyySEq-2y2niDU0ZsFRNfA@mail.gmail.com> (Andrew Zaborowski's message of "Tue, 21 Feb 2017 02:44:10 +0100")
Andrew Zaborowski <andrew.zaborowski@intel.com> writes:
> Hi,
>
> On 15 February 2017 at 09:58, Kalle Valo <kvalo@codeaurora.org> wrote:
>> Johannes Berg <johannes@sipsolutions.net> writes:
>>> On Fri, 2017-02-10 at 10:02 +0100, Andrew Zaborowski wrote:
>>>> Change the SET CQM command's RSSI threshold attribute to accept any
>>>> number of thresholds as a sorted array. The API should be backwards
>>>> compatible so that if one s32 threshold value is passed, the old
>>>> mechanism is enabled. The netlink event generated is the same in
>>>> both cases.
>>>
>>> I've applied this now, thanks for your patience :)
>>>
>>> I got a bit confused - and then fixed it up - patchwork has giving your
>>> name as "Andrzej Zaborowski" which apparently you didn't really want
>>> (any more). I've fixed it for these patches to be as the patches you
>>> sent, but no guarantees I've done this before or will remember to do
>>> that in the future - if you can somehow change your name in patchwork
>>> (patchwork.kernel.org) that would be good.
>
> Thanks, changed it for consistency now.
>
>>
>> IIRC if you haven't registered to patchwork.kernel.org it's possible to
>> change the name easily. But after registration the user needs to contact
>> helpdesk to change the name.
>
> Indeed I was able to set name on registration today but can see no way
> to modify it. The project's mailing list has a thread about a patch
> that's about to be backported to the patchwork.kernel.org version
> though,
> https://github.com/getpatchwork/patchwork/commit/d365402fb98dfb2c4aea4b58346096f85bdfa0c3
Great, that's exactly the right way to fix this. Thanks for letting us
now.
--
Kalle Valo
prev parent reply other threads:[~2017-02-21 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 9:02 [PATCH v6 1/3] cfg80211: Accept multiple RSSI thresholds for CQM Andrew Zaborowski
2017-02-15 8:27 ` Johannes Berg
2017-02-15 8:58 ` Kalle Valo
2017-02-21 1:44 ` Andrew Zaborowski
2017-02-21 8:48 ` Kalle Valo [this message]
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=87d1ecdj5e.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=andrew.zaborowski@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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.