Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Bartosz Markowski <bartosz.markowski@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] ath10k: update wal_dbg_tx_stats structure with missing parameter.
Date: Tue, 3 Sep 2013 10:05:04 +0300	[thread overview]
Message-ID: <87eh961j33.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1377778061-22331-2-git-send-email-bartosz.markowski@tieto.com> (Bartosz Markowski's message of "Thu, 29 Aug 2013 14:07:39 +0200")

Bartosz Markowski <bartosz.markowski@tieto.com> writes:

> It's very imporatant to keep these structs up to date with FW abi,
> due to the arithmetic we use while read the fw_stats.
>
> Signed-off-by: Bartosz Markowski <bartosz.markowski@tieto.com>
> ---
>  drivers/net/wireless/ath/ath10k/wmi.h |    3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/drivers/net/wireless/ath/ath10k/wmi.h b/drivers/net/wireless/ath/ath10k/wmi.h
> index 08860c4..5b94707 100644
> --- a/drivers/net/wireless/ath/ath10k/wmi.h
> +++ b/drivers/net/wireless/ath/ath10k/wmi.h
> @@ -1767,6 +1767,9 @@ struct wal_dbg_tx_stats {
>  	/* wal pdev resets  */
>  	__le32 pdev_resets;
>  
> +	/* frames dropped due to non-availability of stateless TIDs */
> +	__le32 stateless_tid_alloc_failure;
> +
>  	__le32 phy_underrun;

I still wonder if this needs a feature bit. At least you should mention
in the commit log why it's not needed.

-- 
Kalle Valo

  reply	other threads:[~2013-09-03  7:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 12:07 [PATCH v3 0/2] add per-VDEV FW statistics Bartosz Markowski
2013-08-29 12:07 ` [PATCH v3 1/2] ath10k: update wal_dbg_tx_stats structure with missing parameter Bartosz Markowski
2013-09-03  7:05   ` Kalle Valo [this message]
2013-08-29 12:07 ` [PATCH v3 2/2] ath10k: implement per-VDEV FW statistics Bartosz Markowski
2013-09-03  7:13   ` 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=87eh961j33.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=bartosz.markowski@tieto.com \
    --cc=linux-wireless@vger.kernel.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