ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: Maharaja Kennadyrajan <mkenna@codeaurora.org>
Cc: ath10k@lists.infradead.org,
	Maharaja Kennadyrajan <c_mkenna@qti.qualcomm.com>
Subject: Re: ath10k: tpc_stats(_final) odd twicepowers and 160Mhz not supported
Date: Wed, 10 Oct 2018 17:25:09 +0200	[thread overview]
Message-ID: <2105594.XRlnIHHpuj@bentobox> (raw)
In-Reply-To: <1555379.7kbm3L4fcB@bentobox>


[-- Attachment #1.1: Type: text/plain, Size: 708 bytes --]

On Donnerstag, 26. Juli 2018 15:03:54 CEST Sven Eckelmann wrote:
> On Dienstag, 10. Juli 2018 08:52:35 CEST Sven Eckelmann wrote:
> > On Donnerstag, 28. Juni 2018 12:05:18 CEST Sven Eckelmann wrote:
> > > Hi,
> > > 
> > > I have some small question regarding the debugging functionality introduced by 
> > > commit bc64d05220f3 ("ath10k: debugfs support to get final TPC stats for 10.4 
> > > variants") [1] and commit 295426669cd6 ("ath10k: implement debugfs interface 
> > > for Transmit Power Control stats") [2]. Goal of this is to find out whether 
> > > the VHT160 MHz CTLs are correctly applied.
> > [...]
> > 
> > ping?
> 
> ping?

Ping? I think we can already declaring you MIA.

Kind regards,
	Sven

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

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

      reply	other threads:[~2018-10-10 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 10:05 ath10k: tpc_stats(_final) odd twicepowers and 160Mhz not supported Sven Eckelmann
2018-07-10  6:52 ` Sven Eckelmann
2018-07-26 13:03   ` Sven Eckelmann
2018-10-10 15:25     ` Sven Eckelmann [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=2105594.XRlnIHHpuj@bentobox \
    --to=sven.eckelmann@openmesh.com \
    --cc=ath10k@lists.infradead.org \
    --cc=c_mkenna@qti.qualcomm.com \
    --cc=mkenna@codeaurora.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