From: Kalle Valo <kvalo@kernel.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: <mhi@lists.linux.dev>, <ath11k@lists.infradead.org>,
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v4 2/3] wifi: ath11k: qmi: refactor ath11k_qmi_m3_load()
Date: Thu, 19 Oct 2023 12:53:36 +0300 [thread overview]
Message-ID: <87ttqn0wgv.fsf@kernel.org> (raw)
In-Reply-To: <d86d8f47-dbb2-1da6-794a-c020c317b4b5@quicinc.com> (Jeff Johnson's message of "Thu, 27 Jul 2023 09:47:21 -0700")
Jeff Johnson <quic_jjohnson@quicinc.com> writes:
> On 7/27/2023 3:04 AM, Kalle Valo wrote:
>> From: Kalle Valo <quic_kvalo@quicinc.com>
>> Simple refactoring to make it easier to add firmware-2.bin support
>> in the
>> following patch.
>> Earlier ath11k_qmi_m3_load() supported changing m3.bin contents
>> while ath11k is
>> running. But that's not going to actually work, m3.bin is supposed to the be
>
> nit: s/to the be/to be the/
Fixed in the pending branch, thanks.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-10-19 9:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 10:04 [PATCH v4 0/3] wifi: ath11k: support firmware-2.bin Kalle Valo
2023-07-27 10:04 ` [PATCH v4 1/3] bus: mhi: host: allow MHI client drivers to provide the firmware via a pointer Kalle Valo
2023-08-01 4:20 ` Jeffrey Hugo
2023-08-02 11:01 ` Manivannan Sadhasivam
2023-08-03 18:31 ` Kalle Valo
2023-08-04 6:40 ` Manivannan Sadhasivam
2023-07-27 10:04 ` [PATCH v4 2/3] wifi: ath11k: qmi: refactor ath11k_qmi_m3_load() Kalle Valo
2023-07-27 16:47 ` Jeff Johnson
2023-10-19 9:53 ` Kalle Valo [this message]
2023-10-25 9:54 ` Kalle Valo
2023-07-27 10:04 ` [PATCH v4 3/3] wifi: ath11k: add firmware-2.bin support Kalle Valo
2023-07-27 17:12 ` Jeff Johnson
2023-10-19 13:27 ` Kalle Valo
2023-10-19 15:22 ` Jeff Johnson
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=87ttqn0wgv.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mhi@lists.linux.dev \
--cc=quic_jjohnson@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).