From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: bugs@lists.linux.dev, linux-wireless@vger.kernel.org,
quic_msinada@quicinc.com, ath11k@lists.infradead.org
Subject: Re: wifi: ath11k: push MU-MIMO configurations to hardware
Date: Wed, 5 Apr 2023 08:25:00 +0000 (UTC) [thread overview]
Message-ID: <20230405-b217299-ec3c4e9b0c8a@bugzilla.kernel.org> (raw)
In-Reply-To: <1666128501-12364-1-git-send-email-quic_msinada@quicinc.com>
Hello:
This conversation is now tracked by Kernel.org Bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=217299
There is no need to do anything else, just keep talking.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
parent reply other threads:[~2023-04-05 8:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1666128501-12364-1-git-send-email-quic_msinada@quicinc.com>]
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=20230405-b217299-ec3c4e9b0c8a@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=bugs@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_msinada@quicinc.com \
/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 NNTP newsgroup(s).