From: Kalle Valo <kvalo@codeaurora.org>
To: Bhaumik Bhatt <bbhatt@codeaurora.org>
Cc: manivannan.sadhasivam@linaro.org, linux-arm-msm@vger.kernel.org,
hemantk@codeaurora.org, jhugo@codeaurora.org,
linux-kernel@vger.kernel.org, ath11k@lists.infradead.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath11k: use MHI provided APIs to allocate and free MHI controller
Date: Tue, 17 Nov 2020 09:14:58 +0200 [thread overview]
Message-ID: <87tutozc7h.fsf@codeaurora.org> (raw)
In-Reply-To: <1605571300-4438-1-git-send-email-bbhatt@codeaurora.org> (Bhaumik Bhatt's message of "Mon, 16 Nov 2020 16:01:40 -0800")
Bhaumik Bhatt <bbhatt@codeaurora.org> writes:
> Use MHI provided APIs to allocate and free MHI controller to
> improve MHI host driver handling.
How does it improve the handling?
> This also fixes a memory leak as the MHI controller was allocated but
> never freed.
>
> Signed-off-by: Bhaumik Bhatt <bbhatt@codeaurora.org>
> ---
> drivers/net/wireless/ath/ath11k/mhi.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
For ath11k patches please CC ath11k and linux-wireless lists so that
patchwork sees it. So you need to resend this.
Is this a new API? I need to understand if there are any dependencies
between mhi and ath trees, or if I can apply this directly to my ath.git
tree.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-11-17 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 0:01 [PATCH] ath11k: use MHI provided APIs to allocate and free MHI controller Bhaumik Bhatt
2020-11-17 3:36 ` Manivannan Sadhasivam
2020-11-17 7:14 ` Kalle Valo [this message]
2020-11-17 17:17 ` Bhaumik Bhatt
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=87tutozc7h.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=bbhatt@codeaurora.org \
--cc=hemantk@codeaurora.org \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
/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