From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Jiri Kosina <trivial@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
"John W. Linville" <linville@tuxdriver.com>
Subject: [PATCH/TRIVIAL 3/4] iwlegacy: 4965-rs: Remove bogus colon after newline from debug message
Date: Thu, 23 Oct 2014 11:52:56 +0200 [thread overview]
Message-ID: <1414057977-4191-3-git-send-email-geert+renesas@glider.be> (raw)
In-Reply-To: <1414057977-4191-1-git-send-email-geert+renesas@glider.be>
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: John W. Linville <linville@tuxdriver.com>
---
drivers/net/wireless/iwlegacy/4965-rs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/iwlegacy/4965-rs.c b/drivers/net/wireless/iwlegacy/4965-rs.c
index eaaeea19d8c5bcc9..bac60b2bc3f014a5 100644
--- a/drivers/net/wireless/iwlegacy/4965-rs.c
+++ b/drivers/net/wireless/iwlegacy/4965-rs.c
@@ -1678,7 +1678,7 @@ il4965_rs_stay_in_table(struct il_lq_sta *lq_sta, bool force_search)
lq_sta->total_success > lq_sta->max_success_limit ||
(!lq_sta->search_better_tbl && lq_sta->flush_timer &&
flush_interval_passed)) {
- D_RATE("LQ: stay is expired %d %d %d\n:",
+ D_RATE("LQ: stay is expired %d %d %d\n",
lq_sta->total_failed, lq_sta->total_success,
flush_interval_passed);
--
1.9.1
next prev parent reply other threads:[~2014-10-23 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 9:52 [PATCH/TRIVIAL 1/4] cpufreq: cpufreq-dt: Move newline to end of error message Geert Uytterhoeven
2014-10-23 9:52 ` [PATCH/TRIVIAL 2/4] drm/i915: " Geert Uytterhoeven
2014-10-23 9:52 ` Geert Uytterhoeven [this message]
2014-10-23 9:52 ` [PATCH/TRIVIAL 4/4] uwb: Remove bogus colon after newline from debug message Geert Uytterhoeven
2014-11-19 8:06 ` [PATCH/TRIVIAL 1/4] cpufreq: cpufreq-dt: Move newline to end of error message Viresh Kumar
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=1414057977-4191-3-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=trivial@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;
as well as URLs for NNTP newsgroup(s).