Compex WLE200NX: regdomain sanitized regression

Kalle Valo kvalo at
Thu Feb 24 08:47:08 PST 2022

Thorsten Leemhuis <regressions at> writes:

> On 24.02.22 17:22, Kalle Valo wrote:
>> Thorsten Leemhuis <regressions at> writes:
>>> Hi, this is your Linux kernel regression tracker speaking. Top-posting
>>> for once, to make this easy accessible to everyone.
>>> Kalle, thx for looking into this, I'm well aware this is kinda tricky.
>>> This is a gently reminder about the issue to ensure it doesn't fall
>>> through the cracks. At the same time I know that it's not urgent, that
>>> why I'm not putting it on backburner in regzbot now:
>>> #regzbot backburner: tricky situation and around for a while, hence not
>>> that urgent
>>> #regzbot poke
>>> I'll likely sent another gentle reminder after the next merge-window.
>> I now queued the revert to my pending branch:
> Ohh, great, many thx!
>> Thorsten, can you please check that the Link tag is correct so that
>> regzbot can automatically detect the fix?
> Yeah, it will, thx to the "Link:

Great, thanks for checking.

> The kernel's docs say the redirector should be used in such cases (so
> "/r/" instead of "/all/"), but regzbot doesn't care about it -- and I
> wonder if that detail is actually important anyway now that we have

Funny that you ask, I was just few minutes ago updating my emacs
function which creates the lore link and was wondering the same. It
looks like '/r/' redirects to '/all/', so I guess we should use the
latter now:

$ curl --head
HTTP/1.1 302 Found
Server: nginx
Date: Thu, 24 Feb 2022 16:43:32 GMT
Content-Type: text/plain
Connection: keep-alive

But yeah, it shouldn't matter as hopefully all sane tools can handle


More information about the ath10k mailing list