From: Kalle Valo <kvalo@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Nuno Oliveira <nuno@eq.uc.pt>,
Sebastian Bachmann <hello@reox.at>,
wgong@codeaurora.org, ath10k@lists.infradead.org,
"regressions\@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: Compex WLE200NX: regdomain sanitized regression
Date: Thu, 24 Feb 2022 18:47:08 +0200 [thread overview]
Message-ID: <87k0dktdo3.fsf@kernel.org> (raw)
In-Reply-To: <cf56111a-e6f6-249b-4953-25159420e99d@leemhuis.info> (Thorsten Leemhuis's message of "Thu, 24 Feb 2022 17:38:10 +0100")
Thorsten Leemhuis <regressions@leemhuis.info> writes:
> On 24.02.22 17:22, Kalle Valo wrote:
>> Thorsten Leemhuis <regressions@leemhuis.info> 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:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=dfc438d224e4ad756b276d79e5771c45b523156d
>
> 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:
> https://lore.kernel.org/all/1c160dfb-6ccc-b4d6-76f6-4364e0adb6dd@reox.at/".
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
> lore.kernel.org/all/.
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 https://lore.kernel.org/r/1c160dfb-6ccc-b4d6-76f6-4364e0adb6dd@reox.at/
HTTP/1.1 302 Found
Server: nginx
Date: Thu, 24 Feb 2022 16:43:32 GMT
Content-Type: text/plain
Connection: keep-alive
Location: https://lore.kernel.org/all/1c160dfb-6ccc-b4d6-76f6-4364e0adb6dd@reox.at/
But yeah, it shouldn't matter as hopefully all sane tools can handle
both.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Nuno Oliveira <nuno@eq.uc.pt>, Sebastian Bachmann <hello@reox.at>,
wgong@codeaurora.org, ath10k@lists.infradead.org,
"regressions\@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: Compex WLE200NX: regdomain sanitized regression
Date: Thu, 24 Feb 2022 18:47:08 +0200 [thread overview]
Message-ID: <87k0dktdo3.fsf@kernel.org> (raw)
In-Reply-To: <cf56111a-e6f6-249b-4953-25159420e99d@leemhuis.info> (Thorsten Leemhuis's message of "Thu, 24 Feb 2022 17:38:10 +0100")
Thorsten Leemhuis <regressions@leemhuis.info> writes:
> On 24.02.22 17:22, Kalle Valo wrote:
>> Thorsten Leemhuis <regressions@leemhuis.info> 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:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=dfc438d224e4ad756b276d79e5771c45b523156d
>
> 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:
> https://lore.kernel.org/all/1c160dfb-6ccc-b4d6-76f6-4364e0adb6dd@reox.at/".
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
> lore.kernel.org/all/.
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 https://lore.kernel.org/r/1c160dfb-6ccc-b4d6-76f6-4364e0adb6dd@reox.at/
HTTP/1.1 302 Found
Server: nginx
Date: Thu, 24 Feb 2022 16:43:32 GMT
Content-Type: text/plain
Connection: keep-alive
Location: https://lore.kernel.org/all/1c160dfb-6ccc-b4d6-76f6-4364e0adb6dd@reox.at/
But yeah, it shouldn't matter as hopefully all sane tools can handle
both.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2022-02-24 16:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 8:17 Compex WLE200NX: regdomain sanitized regression Sebastian Bachmann
2021-11-27 11:28 ` Thorsten Leemhuis
2021-11-27 11:28 ` Thorsten Leemhuis
2021-11-27 12:21 ` Nuno Oliveira
2021-11-27 13:25 ` Sebastian Bachmann
2021-12-01 9:06 ` Thorsten Leemhuis
2021-12-01 9:06 ` Thorsten Leemhuis
2021-12-06 7:18 ` Sebastian Bachmann
2021-12-20 10:37 ` Kalle Valo
2021-12-20 10:37 ` Kalle Valo
2021-12-20 18:31 ` Nuno Oliveira
2021-12-20 18:31 ` Nuno Oliveira
2022-02-18 11:47 ` Thorsten Leemhuis
2022-02-18 11:47 ` Thorsten Leemhuis
2022-02-24 16:22 ` Kalle Valo
2022-02-24 16:22 ` Kalle Valo
2022-02-24 16:38 ` Thorsten Leemhuis
2022-02-24 16:38 ` Thorsten Leemhuis
2022-02-24 16:47 ` Kalle Valo [this message]
2022-02-24 16:47 ` Kalle Valo
2021-11-27 16:35 ` Bryce Allen
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=87k0dktdo3.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=hello@reox.at \
--cc=nuno@eq.uc.pt \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=wgong@codeaurora.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.