From: Kalle Valo <kvalo@kernel.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: Jeff Johnson <jjohnson@kernel.org>,
<linux-wireless@vger.kernel.org>, <ath11k@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Jeff Johnson <quic_jjohnson@quicinc.com>
Subject: Re: [PATCH 1/2] wifi: ath11k: refactor CE remap & unmap
Date: Fri, 3 May 2024 13:15:28 +0000 (UTC) [thread overview]
Message-ID: <171474212652.1512332.14638586836562362719.kvalo@kernel.org> (raw)
In-Reply-To: <20240430-ce-unmap-v1-1-e468328f95d9@quicinc.com>
Jeff Johnson <quic_jjohnson@quicinc.com> wrote:
> Currently the logic that handles hw_params->ce_remap is inline code,
> both for doing the remap and the unmap. An upcoming change needs to do
> the unmap in a second place, so refactor the unmap logic into a
> separate function. And although it is only called from one place,
> refactor the remap logic as well to have functional symmetry.
>
> No functional changes, compile tested only.
>
> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
> Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com>
2 patches applied to ath-next branch of ath.git, thanks.
8b9ea752a9d6 wifi: ath11k: refactor CE remap & unmap
c57d00a4d3d8 wifi: ath11k: unmap the CE in ath11k_ahb_probe() error path
--
https://patchwork.kernel.org/project/linux-wireless/patch/20240430-ce-unmap-v1-1-e468328f95d9@quicinc.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-05-03 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 13:30 [PATCH 0/2] wifi: ath11k: fix ioremap() leak Jeff Johnson
2024-04-30 13:30 ` [PATCH 1/2] wifi: ath11k: refactor CE remap & unmap Jeff Johnson
2024-05-03 13:15 ` Kalle Valo [this message]
2024-04-30 13:30 ` [PATCH 2/2] wifi: ath11k: unmap the CE in ath11k_ahb_probe() error path 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=171474212652.1512332.14638586836562362719.kvalo@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).