public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "santosh.anbu" <asantoshking@gmail.com>
To: airlied@linux.ie
Cc: asantosh.king@gmail.com, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] i2c.c: Fixed coding style issue for if statement
Date: Sat, 27 Jul 2013 23:18:36 +0530	[thread overview]
Message-ID: <1374947316-7864-1-git-send-email-asantosh.king@gmail.com> (raw)

From: "santosh.anbu" <asantosh.king@gmail.com>

Fixed coding style issue

Signed-off-by: santosh.anbu <asantosh.king@gmail.com>
---
 drivers/gpu/drm/nouveau/core/subdev/bios/i2c.c | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/drivers/gpu/drm/nouveau/core/subdev/bios/i2c.c b/drivers/gpu/drm/nouveau/core/subdev/bios/i2c.c
index cfb9288..e88529c 100644
--- a/drivers/gpu/drm/nouveau/core/subdev/bios/i2c.c
+++ b/drivers/gpu/drm/nouveau/core/subdev/bios/i2c.c
@@ -114,15 +114,19 @@ dcb_i2c_parse(struct nouveau_bios *bios, u8 idx, struct dcb_i2c_entry *info)
 
 		if (idx == 0) {
 			info->drive = nv_ro08(bios, ent + 4);
-			if (!info->drive) info->drive = 0x3f;
+			if (!info->drive)
+				info->drive = 0x3f;
 			info->sense = nv_ro08(bios, ent + 5);
-			if (!info->sense) info->sense = 0x3e;
+			if (!info->sense)
+				info->sense = 0x3e;
 		} else
 		if (idx == 1) {
 			info->drive = nv_ro08(bios, ent + 6);
-			if (!info->drive) info->drive = 0x37;
+			if (!info->drive)
+				info->drive = 0x37;
 			info->sense = nv_ro08(bios, ent + 7);
-			if (!info->sense) info->sense = 0x36;
+			if (!info->sense)
+				info->sense = 0x36;
 		}
 
 		info->type  = DCB_I2C_NV04_BIT;
-- 
1.8.1.2


             reply	other threads:[~2013-07-27 17:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-27 17:48 santosh.anbu [this message]
2013-07-27 17:53 ` [PATCH 2/2] i2c.c: Fixed coding style issue for if statement Joe Perches

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=1374947316-7864-1-git-send-email-asantosh.king@gmail.com \
    --to=asantoshking@gmail.com \
    --cc=airlied@linux.ie \
    --cc=asantosh.king@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --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