All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Fabio Estevam <festevam@denx.de>
Cc: Kalle Valo <kvalo@codeaurora.org>,
	ath10k@lists.infradead.org,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	erik.stromdahl@gmail.com, Peter Oh <peter.oh@eero.com>,
	Arend van Spriel <aspriel@gmail.com>, Marek Vasut <marex@denx.de>,
	alagusankar@silex-india.com
Subject: Re: [PATCH v3] ath10k: high latency fixes for beacon buffer
Date: Thu, 26 Aug 2021 09:01:27 -0300	[thread overview]
Message-ID: <CAOMZO5CJC0=iH4zzJGj0e82GexBN7suOehz8ajKK8bK3ZcMOSg@mail.gmail.com> (raw)
In-Reply-To: <20210818232627.2040121-1-festevam@denx.de>

Hello Kalle,

On Wed, Aug 18, 2021 at 8:27 PM Fabio Estevam <festevam@denx.de> wrote:
>
> From: Alagu Sankar <alagusankar@silex-india.com>
>
> 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>
> ---
> Changes since v2:
> - Pick Alagu's patch:
> https://patchwork.kernel.org/project/ath10k/patch/20190417191503.18814-3-erik.stromdahl@gmail.com/

A gentle ping on this one.

WARNING: multiple messages have this Message-ID (diff)
From: Fabio Estevam <festevam@gmail.com>
To: Fabio Estevam <festevam@denx.de>
Cc: Kalle Valo <kvalo@codeaurora.org>,
	ath10k@lists.infradead.org,
	 linux-wireless <linux-wireless@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	erik.stromdahl@gmail.com,  Peter Oh <peter.oh@eero.com>,
	Arend van Spriel <aspriel@gmail.com>, Marek Vasut <marex@denx.de>,
	alagusankar@silex-india.com
Subject: Re: [PATCH v3] ath10k: high latency fixes for beacon buffer
Date: Thu, 26 Aug 2021 09:01:27 -0300	[thread overview]
Message-ID: <CAOMZO5CJC0=iH4zzJGj0e82GexBN7suOehz8ajKK8bK3ZcMOSg@mail.gmail.com> (raw)
In-Reply-To: <20210818232627.2040121-1-festevam@denx.de>

Hello Kalle,

On Wed, Aug 18, 2021 at 8:27 PM Fabio Estevam <festevam@denx.de> wrote:
>
> From: Alagu Sankar <alagusankar@silex-india.com>
>
> 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>
> ---
> Changes since v2:
> - Pick Alagu's patch:
> https://patchwork.kernel.org/project/ath10k/patch/20190417191503.18814-3-erik.stromdahl@gmail.com/

A gentle ping on this one.

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  parent reply	other threads:[~2021-08-26 12:01 UTC|newest]

Thread overview: 9+ 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-18 23:26 ` Fabio Estevam
2021-08-20  6:45 ` kernel test robot
2021-08-26 12:01 ` Fabio Estevam [this message]
2021-08-26 12:01   ` Fabio Estevam
2021-09-16 12:38   ` Kalle Valo
2021-09-16 12:38     ` Kalle Valo
2021-09-28 14:34 ` Kalle Valo
2021-09-28 14:34 ` Kalle Valo

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='CAOMZO5CJC0=iH4zzJGj0e82GexBN7suOehz8ajKK8bK3ZcMOSg@mail.gmail.com' \
    --to=festevam@gmail.com \
    --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=kvalo@codeaurora.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.