From: Gertjan van Wingerde <gwingerde@gmail.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>, linux-wireless@vger.kernel.org
Cc: users@rt2x00.serialmonkey.com
Subject: Re: [rt2x00-users] [PATCH] rt2x00: move frequent messages to debug level
Date: Sun, 02 Feb 2014 23:14:35 +0100 [thread overview]
Message-ID: <52EEC34B.2030208@gmail.com> (raw)
In-Reply-To: <1391170689-23038-1-git-send-email-sgruszka@redhat.com>
On 01/31/14 13:18, Stanislaw Gruszka wrote:
> On commit 28f2bce9f8bbf704c86f8c684337f82c51592c81 I make change that
> print various messages as default. This can cause flood of messages
> related to TX status timeout on some environments. I partially fixed
> problem on commit bb9c298f3193ac5b80e47b325c690700580b6bcf, but forgot
> to move two more messages to debug level.
>
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
Acked-by: Gertjan van Wingerde <gwingerde@gmail.com>
> ---
> drivers/net/wireless/rt2x00/rt2800usb.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/wireless/rt2x00/rt2800usb.c b/drivers/net/wireless/rt2x00/rt2800usb.c
> index caddc1b..14a90dd 100644
> --- a/drivers/net/wireless/rt2x00/rt2800usb.c
> +++ b/drivers/net/wireless/rt2x00/rt2800usb.c
> @@ -125,9 +125,9 @@ static inline bool rt2800usb_entry_txstatus_timeout(struct queue_entry *entry)
>
> tout = time_after(jiffies, entry->last_action + msecs_to_jiffies(100));
> if (unlikely(tout))
> - rt2x00_warn(entry->queue->rt2x00dev,
> - "TX status timeout for entry %d in queue %d\n",
> - entry->entry_idx, entry->queue->qid);
> + rt2x00_dbg(entry->queue->rt2x00dev,
> + "TX status timeout for entry %d in queue %d\n",
> + entry->entry_idx, entry->queue->qid);
> return tout;
>
> }
> @@ -566,8 +566,8 @@ static void rt2800usb_txdone(struct rt2x00_dev *rt2x00dev)
> queue = rt2x00queue_get_tx_queue(rt2x00dev, qid);
>
> if (unlikely(rt2x00queue_empty(queue))) {
> - rt2x00_warn(rt2x00dev, "Got TX status for an empty queue %u, dropping\n",
> - qid);
> + rt2x00_dbg(rt2x00dev, "Got TX status for an empty queue %u, dropping\n",
> + qid);
> break;
> }
>
>
--
---
Gertjan
prev parent reply other threads:[~2014-02-02 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 12:18 [PATCH] rt2x00: move frequent messages to debug level Stanislaw Gruszka
2014-02-02 22:14 ` Gertjan van Wingerde [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=52EEC34B.2030208@gmail.com \
--to=gwingerde@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.com \
--cc=users@rt2x00.serialmonkey.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).