From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Kalle Valo <kvalo@kernel.org>
Cc: Jeff Johnson <quic_jjohnson@quicinc.com>,
Linux regressions mailing list <regressions@lists.linux.dev>,
Carl Huang <quic_cjhuang@quicinc.com>,
Luca Weiss <luca.weiss@fairphone.com>,
ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] wifi: ath11k: supports 2 station interfaces
Date: Sun, 19 May 2024 19:51:32 +0200 [thread overview]
Message-ID: <80b102c5-2d49-41ba-a4e3-801e16f7f2bd@leemhuis.info> (raw)
In-Reply-To: <874jawhopo.fsf@kernel.org>
On 17.05.24 09:39, Kalle Valo wrote:
> Thorsten Leemhuis <regressions@leemhuis.info> writes:
>> On 17.05.24 07:25, Kalle Valo wrote:
>>> Jeff Johnson <quic_jjohnson@quicinc.com> writes:
>>>> On 5/16/2024 4:45 AM, Linux regression tracking (Thorsten Leemhuis) wrote:
>>>>> On 11.05.24 05:12, Carl Huang wrote:
>>>>>> I'll send out the formal patch next week.
>>>>>
>>>>> Hmmm, from here it looks like this did not happen. Did I miss something,
>>>>> is there some reason to reevaluate things again, or did this maybe
>>>>> simply fall through the cracks?
>>>>
>>>> Formal patch is still under internal review
>>>
>>> BTW I'm also experimenting with regzbot to help me track regressions in
>>> wireless and to avoid missing important fixes.
>>
>> Not sure, but I tend to think that's still too early; better wait a few
>> more months.
>
> FWIW I have been pretty happy so far and would prefer to continue using
> it with wireless drivers regressions.
Ohh, in that case just continue!
> But of course if it's better for you I'll stop for now.
No, not at all, making regzbot more useful for subsystem developers and
maintainers is the next important step, so I'm glad if it already works
well for you. And if something does not work, just tell me!
>>> Thorsten, I don't know if you take wishes but it would be nice to have
>>> in regzbot some kind of filtering per subsystem or label. Maybe
>>> something like this:
>>> https://linux-regtracking.leemhuis.info/regzbot/mainline/?subsystem=wireless
>>>
>>> And then a have command for regzbot setting the subsystem (or a label).
>>> That way I could easily see only the wireless related regressions, now
>>> it's harder to find them from the list.
>>
>> I listen to wishes, but in this case the idea is not new: exactly
>> something like this is pretty high on my todo list. But there are still
>> two other things on top of it and requires some major reworks; and I
>> currently also don't find much time to work on the code. :-/ But sooner
>> or later I'll get there!
>
> Trust me, I know how it is :) These are just wishlist stuff and low
> priority.
Apparently depends on the point of view, as I think it's high priority.
> One more to the wishlist: refreshing the HTML page once an hour or so. I
> now keep the regzbot page always open and it would be nice to have it
> up-to-date without pressing CTRL-R. Yes, I'm lazy :)
Added that to the issue tracker to ensure it's not forgotten.
Ciao, Thorsten
next prev parent reply other threads:[~2024-05-19 17:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 2:37 [PATCH 0/2] wifi: ath11k: support 2 station interfaces Carl Huang
2023-07-14 2:38 ` [PATCH 1/2] wifi: ath11k: supports " Carl Huang
2024-02-13 16:17 ` Kalle Valo
2024-02-15 11:23 ` Kalle Valo
2024-05-10 8:22 ` Luca Weiss
2024-05-10 10:18 ` Kalle Valo
2024-05-10 12:03 ` Carl Huang
2024-05-10 13:04 ` Carl Huang
2024-05-10 13:26 ` Luca Weiss
2024-05-11 2:50 ` Carl Huang
2024-05-10 13:57 ` Kalle Valo
2024-05-11 3:12 ` Carl Huang
2024-05-16 11:45 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-16 14:11 ` Jeff Johnson
2024-05-17 5:25 ` Kalle Valo
2024-05-17 6:04 ` Thorsten Leemhuis
2024-05-17 7:39 ` Kalle Valo
2024-05-19 17:51 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2024-05-10 11:35 ` Carl Huang
2024-05-10 12:58 ` Luca Weiss
2023-07-14 2:38 ` [PATCH 2/2] wifi: ath11k: reports address list if chip supports 2 stations Carl Huang
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=80b102c5-2d49-41ba-a4e3-801e16f7f2bd@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=quic_cjhuang@quicinc.com \
--cc=quic_jjohnson@quicinc.com \
--cc=regressions@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).