From: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
To: quic_bqiang@quicinc.com
Cc: ath11k@lists.infradead.org, jjohnson@kernel.org,
jtornosm@redhat.com, kvalo@kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wifi: ath11k: workaround to use VMs
Date: Fri, 22 Mar 2024 11:37:53 +0100 [thread overview]
Message-ID: <20240322103756.94296-1-jtornosm@redhat.com> (raw)
In-Reply-To: <87f0c6c9-43e5-4ea3-8f4c-9425e6a74b10@quicinc.com>
Thank you for your comments.
I don't have seen any change in MSI vector data but if it can be different from zero I will complete it.
Best regards
José Ignacio
next prev parent reply other threads:[~2024-03-22 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 17:23 [PATCH] wifi: ath11k: workaround to use VMs Jose Ignacio Tornos Martinez
2024-03-21 20:13 ` Jeff Johnson
2024-03-22 2:17 ` Baochen Qiang
2024-03-22 2:09 ` Baochen Qiang
2024-03-22 10:37 ` Jose Ignacio Tornos Martinez [this message]
2024-03-22 10:49 ` [PATCH V2] " Jose Ignacio Tornos Martinez
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=20240322103756.94296-1-jtornosm@redhat.com \
--to=jtornosm@redhat.com \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_bqiang@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).