From: Adithya Krishnamurthy <linux.challenge1@gmail.com>
To: omar.ramirez@copitl.com, gregkh@linuxfoundation.org,
rashika.kheria@gmail.com, freemangordon@abv.bg,
dan.carpenter@oracle.com, ody.guru@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Cc: Adithya Krishnamurthy <linux.challenge1@gmail.com>
Subject: [PATCH] Staging:tidspbridge Fix minor checkpatch.pl warning unnecessary whitespace before a quoted newline
Date: Tue, 15 Jul 2014 22:18:19 +0530 [thread overview]
Message-ID: <1405442900-6977-2-git-send-email-linux.challenge1@gmail.com> (raw)
In-Reply-To: <1405442900-6977-1-git-send-email-linux.challenge1@gmail.com>
From: Adithya Krishnamurthy <linux.challenge1@gmail.com>
Fixed checkpatch "WARNING: unnecessary whitespace before a quoted newline"
Signed-off-by: Adithya Krishnamurthy <linux.challenge1@gmail.com>
---
drivers/staging/tidspbridge/core/tiomap3430.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/tidspbridge/core/tiomap3430.c b/drivers/staging/tidspbridge/core/tiomap3430.c
index f63dd8f..0559ab6 100644
--- a/drivers/staging/tidspbridge/core/tiomap3430.c
+++ b/drivers/staging/tidspbridge/core/tiomap3430.c
@@ -536,7 +536,7 @@ static int bridge_brd_start(struct bridge_dev_context *dev_ctxt,
if ((unsigned int *)ul_dsp_clk_addr != NULL) {
/* Get the clock rate */
ul_dsp_clk_rate = dsp_clk_get_iva2_rate();
- dev_dbg(bridge, "%s: DSP clock rate (KHZ): 0x%x \n",
+ dev_dbg(bridge, "%s: DSP clock rate (KHZ): 0x%x\n",
__func__, ul_dsp_clk_rate);
(void)bridge_brd_write(dev_context,
(u8 *) &ul_dsp_clk_rate,
--
1.7.9.5
next prev parent reply other threads:[~2014-07-15 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 16:48 [PATCH] Staging:tidspbridge Fix checkpatch.pl warning char * array declaration might be better as static const Adithya Krishnamurthy
2014-07-15 16:48 ` Adithya Krishnamurthy [this message]
2014-07-15 16:48 ` [PATCH] Staging:tidspbridge Fix minor checkpatch.pl warining Unnecessary parentheses Adithya Krishnamurthy
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=1405442900-6977-2-git-send-email-linux.challenge1@gmail.com \
--to=linux.challenge1@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=freemangordon@abv.bg \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ody.guru@gmail.com \
--cc=omar.ramirez@copitl.com \
--cc=rashika.kheria@gmail.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