From: Kalle Valo <kvalo@kernel.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: 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: Fri, 17 May 2024 08:25:03 +0300 [thread overview]
Message-ID: <87fruhggcw.fsf@kernel.org> (raw)
In-Reply-To: <4d72f74a-b2eb-43d3-92a2-1311081ce72c@quicinc.com> (Jeff Johnson's message of "Thu, 16 May 2024 07:11:31 -0700")
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.
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.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-05-17 5:25 UTC|newest]
Thread overview: 24+ 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:37 ` Carl Huang
2023-07-14 2:38 ` [PATCH 1/2] wifi: ath11k: supports " Carl Huang
2023-07-14 2:38 ` 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 [this message]
2024-05-17 6:04 ` Thorsten Leemhuis
2024-05-17 7:39 ` Kalle Valo
2024-05-19 17:51 ` Linux regression tracking (Thorsten Leemhuis)
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
2023-07-14 2:38 ` 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=87fruhggcw.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.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 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.