From: "Sebastian Dalfuß" <sd@sedf.de>
To: greg@kroah.com
Cc: linux-kernel@vger.kernel.org
Subject: [Patch 2/3] staging: rt2860: remove superfluous newlines
Date: Thu, 5 Nov 2009 07:07:25 +0100 [thread overview]
Message-ID: <20091105060725.GB8664@sedf.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2342 bytes --]
From: Sebastian Dalfuß <sd@sedf.de>
Subject: [Patch 2/3] staging: rt2860: remove superfluous newlines
This patch is based on 2.6.32-rc6
This tiny patch removes a few quite unnecessary extra newlines from
DBGPRINT() and printk() strings.
Signed-off-by: Sebastian Dalfuß <sd@sedf.de>
---
diff -ru b/drivers/staging/rt2860/common/dfs.c c/drivers/staging/rt2860/common/dfs.c
--- b/drivers/staging/rt2860/common/dfs.c 2009-11-04 23:32:24.000000000 +0100
+++ c/drivers/staging/rt2860/common/dfs.c 2009-11-05 00:06:25.872076137 +0100
@@ -367,7 +367,7 @@
// channel availability check time is 60sec, use 65 for assurance
if (pAd->CommonCfg.RadarDetect.RDCount++ > pAd->CommonCfg.RadarDetect.ChMovingTime)
{
- DBGPRINT(RT_DEBUG_TRACE, ("Not found radar signal, start send beacon and radar detection in service monitor\n\n"));
+ DBGPRINT(RT_DEBUG_TRACE, ("Not found radar signal, start send beacon and radar detection in service monitor\n"));
BbpRadarDetectionStop(pAd);
AsicEnableBssSync(pAd);
pAd->CommonCfg.RadarDetect.RDMode = RD_NORMAL_MODE;
diff -ru b/drivers/staging/rt2860/common/rtmp_init.c c/drivers/staging/rt2860/common/rtmp_init.c
--- b/drivers/staging/rt2860/common/rtmp_init.c 2009-11-04 23:32:24.000000000 +0100
+++ c/drivers/staging/rt2860/common/rtmp_init.c 2009-11-05 00:05:45.312078083 +0100
@@ -244,7 +244,7 @@
break;
}
pAd->BeaconBuf = pBeaconBuf;
- printk("\n\n=== pAd = %p, size = %d ===\n\n", pAd, (UINT32)sizeof(RTMP_ADAPTER));
+ printk("=== pAd = %p, size = %d ===\n", pAd, (UINT32)sizeof(RTMP_ADAPTER));
// Init spin locks
@@ -3031,7 +3031,7 @@
if (Index > 1000)
{
Status = NDIS_STATUS_FAILURE;
- DBGPRINT(RT_DEBUG_ERROR, ("NICLoadFirmware: MCU is not ready\n\n\n"));
+ DBGPRINT(RT_DEBUG_ERROR, ("NICLoadFirmware: MCU is not ready\n"));
} /* End of if */
DBGPRINT(RT_DEBUG_TRACE,
diff -ru b/drivers/staging/rt2860/rt_linux.c c/drivers/staging/rt2860/rt_linux.c
--- b/drivers/staging/rt2860/rt_linux.c 2009-11-04 23:32:24.000000000 +0100
+++ c/drivers/staging/rt2860/rt_linux.c 2009-11-05 00:07:10.402917865 +0100
@@ -384,7 +384,7 @@
{
*ppPacket = NULL;
#ifdef DEBUG
- printk("RTMPAllocateNdisPacket Fail\n\n");
+ printk("RTMPAllocateNdisPacket Fail\n");
#endif
return NDIS_STATUS_FAILURE;
}
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2009-11-05 6:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20091105060725.GB8664@sedf.de \
--to=sd@sedf.de \
--cc=greg@kroah.com \
--cc=linux-kernel@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
Powered by JetHome