From: Kalle Valo <kvalo@codeaurora.org>
To: Fabio Estevam <festevam@denx.de>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
hch@lst.de, erik.stromdahl@gmail.com, peter.oh@eero.com,
aspriel@gmail.com, marex@denx.de, alagusankar@silex-india.com,
Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH v3] ath10k: high latency fixes for beacon buffer
Date: Tue, 28 Sep 2021 14:34:44 +0000 (UTC) [thread overview]
Message-ID: <20210928143444.C801DC43460@smtp.codeaurora.org> (raw)
In-Reply-To: <20210818232627.2040121-1-festevam@denx.de>
Fabio Estevam <festevam@denx.de> wrote:
> Beacon buffer for high latency devices does not use DMA. other similar
> buffer allocation methods in the driver have already been modified for
> high latency path. Fix the beacon buffer allocation left out in the
> earlier high latency changes.
>
> Signed-off-by: Alagu Sankar <alagusankar@silex-india.com>
> Signed-off-by: Erik Stromdahl <erik.stromdahl@gmail.com>
> [fabio: adapt it to use ar->bus_param.dev_type ]
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
e263bdab9c0e ath10k: high latency fixes for beacon buffer
--
https://patchwork.kernel.org/project/linux-wireless/patch/20210818232627.2040121-1-festevam@denx.de/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2021-09-28 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 23:26 [PATCH v3] ath10k: high latency fixes for beacon buffer Fabio Estevam
2021-08-26 12:01 ` Fabio Estevam
2021-09-16 12:38 ` Kalle Valo
2021-09-28 14:34 ` Kalle Valo [this message]
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=20210928143444.C801DC43460@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=alagusankar@silex-india.com \
--cc=aspriel@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=erik.stromdahl@gmail.com \
--cc=festevam@denx.de \
--cc=hch@lst.de \
--cc=linux-wireless@vger.kernel.org \
--cc=marex@denx.de \
--cc=peter.oh@eero.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).