All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath10k: kill static int max_delay
Date: Wed, 24 Apr 2013 14:20:40 +0300	[thread overview]
Message-ID: <87d2tk6upj.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1366786169-19374-1-git-send-email-janusz.dziedzic@tieto.com> (Janusz Dziedzic's message of "Wed, 24 Apr 2013 08:49:29 +0200")

Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:

> Kill static variable max_delay.
> Move this to struct ath10k_pci.
>
> Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>
> ---
>  drivers/net/wireless/ath/ath10k/pci.c |    5 ++---
>  drivers/net/wireless/ath/ath10k/pci.h |    2 ++
>  2 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath10k/pci.c b/drivers/net/wireless/ath/ath10k/pci.c
> index 0d1523b..9ee678a 100644
> --- a/drivers/net/wireless/ath/ath10k/pci.c
> +++ b/drivers/net/wireless/ath/ath10k/pci.c
> @@ -445,7 +445,6 @@ void ath10k_do_pci_wake(struct ath10k *ar)
>  {
>  	struct ath10k_pci *ar_pci = ath10k_pci_priv(ar);
>  	void __iomem *pci_addr = ar_pci->mem;
> -	static int max_delay;
>  	int tot_delay = 0;
>  	int curr_delay = 5;
>  
> @@ -475,8 +474,8 @@ void ath10k_do_pci_wake(struct ath10k *ar)
>  			curr_delay += 5;
>  	}
>  
> -	if (tot_delay > max_delay)
> -		max_delay = tot_delay;
> +	if (tot_delay > ar_pci->max_delay)
> +		ar_pci->max_delay = tot_delay;
>  }

But do we use this max_delay value for anything sensible? The way I see
it we only store values but don't do anything with it. Unless I'm
missing something, of course.

-- 
Kalle Valo

  reply	other threads:[~2013-04-24 11:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24  6:49 [ath9k-devel] [PATCH] ath10k: kill static int max_delay Janusz Dziedzic
2013-04-24 11:20 ` Kalle Valo [this message]
2013-04-24 11:27   ` Janusz.Dziedzic at tieto.com

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=87d2tk6upj.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath9k-devel@lists.ath9k.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 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.