LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Klaas Neirinck <klaas.neirinck@gmail.com>
To: gregkh@suse.de
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	Klaas Neirinck <klaas.neirinck@gmail.com>
Subject: [PATCH 04/10] Staging: tidspbridge: fixed indent coding style issue
Date: Thu, 17 Feb 2011 03:58:48 +0100	[thread overview]
Message-ID: <1297911534-31534-4-git-send-email-klaas.neirinck@gmail.com> (raw)
In-Reply-To: <1297911534-31534-3-git-send-email-klaas.neirinck@gmail.com>

Fixed coding style issue.

Signed-off-by: Klaas Neirinck <klaas.neirinck@gmail.com>

diff --git a/drivers/staging/tidspbridge/core/tiomap3430.c b/drivers/staging/tidspbridge/core/tiomap3430.c
index eef149b..51cae1a 100644
--- a/drivers/staging/tidspbridge/core/tiomap3430.c
+++ b/drivers/staging/tidspbridge/core/tiomap3430.c
@@ -567,21 +567,21 @@ static int bridge_brd_start(struct bridge_dev_context *dev_ctxt,
 
 	}
 	if (!status) {
-/*PM_IVA2GRPSEL_PER = 0xC0;*/
+		/*PM_IVA2GRPSEL_PER = 0xC0;*/
 		temp = readl(resources->dw_per_pm_base + 0xA8);
 		temp = (temp & 0xFFFFFF30) | 0xC0;
 		writel(temp, resources->dw_per_pm_base + 0xA8);
 
-/*PM_MPUGRPSEL_PER &= 0xFFFFFF3F; */
+		/*PM_MPUGRPSEL_PER &= 0xFFFFFF3F; */
 		temp = readl(resources->dw_per_pm_base + 0xA4);
 		temp = (temp & 0xFFFFFF3F);
 		writel(temp, resources->dw_per_pm_base + 0xA4);
-/*CM_SLEEPDEP_PER |= 0x04; */
+		/*CM_SLEEPDEP_PER |= 0x04; */
 		temp = readl(resources->dw_per_base + 0x44);
 		temp = (temp & 0xFFFFFFFB) | 0x04;
 		writel(temp, resources->dw_per_base + 0x44);
 
-/*CM_CLKSTCTRL_IVA2 = 0x00000003 -To Allow automatic transitions */
+		/*CM_CLKSTCTRL_IVA2 = 0x00000003 -To Allow automatic transitions */
 		(*pdata->dsp_cm_write)(OMAP34XX_CLKSTCTRL_ENABLE_AUTO,
 					OMAP3430_IVA2_MOD, OMAP2_CM_CLKSTCTRL);
 
-- 
1.7.1


  reply	other threads:[~2011-02-17  2:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17  2:58 [PATCH 01/10] Staging: tidspbridge: fixed a brace " Klaas Neirinck
2011-02-17  2:58 ` [PATCH 02/10] Staging: tidspbridge: fixed an include issue changing asm/atomic.h to linux/atomic.h Klaas Neirinck
2011-02-17  2:58   ` [PATCH 03/10] Staging: tidspbridge: fixed unnecessary whitespaces before quoted newlines Klaas Neirinck
2011-02-17  2:58     ` Klaas Neirinck [this message]
2011-02-17  2:58       ` [PATCH 05/10] Staging: tidspbridge: fixed extern in .c file Klaas Neirinck
2011-02-17  2:58         ` [PATCH 06/10] Staging: tidspbridge: fixed spaces before tabs issues Klaas Neirinck
2011-02-17  2:58           ` [PATCH 07/10] Staging: tidspbridge: fixed spaces at the start of a line coding style issues Klaas Neirinck
2011-02-17  2:58             ` [PATCH 08/10] Staging: tidspbridge: fixed missing space after struct definition Klaas Neirinck
2011-02-17  2:58               ` [PATCH 09/10] Staging: tidspbridge: fixed spaces after '*' style issues Klaas Neirinck
2011-02-17  2:58                 ` [PATCH 10/10] Staging: tidspbridge: fixed casting style issue Klaas Neirinck
2011-02-18 21:27 ` [PATCH 01/10] Staging: tidspbridge: fixed a brace coding " Greg KH
2011-02-19  2:24   ` Klaas Neirinck
2011-02-19  5:34     ` Greg KH

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=1297911534-31534-4-git-send-email-klaas.neirinck@gmail.com \
    --to=klaas.neirinck@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH 04/10] Staging: tidspbridge: fixed indent coding style issue' \
    /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

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).