All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeffrin Jose <ahiliation@yahoo.co.in>
To: netdev@vger.kernel.org
Cc: ahiliation@yahoo.co.in
Subject: [PATCH] fixed coding style issue
Date: Sun, 8 Apr 2012 21:37:42 +0530	[thread overview]
Message-ID: <20120408160742.GA4613@debian.Jeff> (raw)

[-- Attachment #1: Type: text/plain, Size: 228 bytes --]

hello all,


i have worked on some coding style issues
on net/core/utils.c

please see attachment.

Thanks

/Jeffrin.

-- 
software engineer
Bohr Lab
department of computer science
Rajagiri school of engineering and technology.

[-- Attachment #2: 0006-net-Fixed-coding-style-issues-relating-to-braces.patch --]
[-- Type: text/x-diff, Size: 963 bytes --]

>From fa37bfd6c2ef8ff81b38ad9dd4467a727d6def81 Mon Sep 17 00:00:00 2001
From: Jeffrin Jose <ahiliation@yahoo.co.in>
Date: Sun, 8 Apr 2012 00:09:11 +0530
Subject: [PATCH 6/6] net: Fixed coding style issues relating to braces.

Fixed coding style issues in net/core/utils.c
in relation with braces placement.
Signed-off-by: Jeffrin Jose <ahiliation@yahoo.co.in>
---
 net/core/utils.c |    9 +++------
 1 files changed, 3 insertions(+), 6 deletions(-)

diff --git a/net/core/utils.c b/net/core/utils.c
index 386e263f..c2e8b41 100644
--- a/net/core/utils.c
+++ b/net/core/utils.c
@@ -59,14 +59,11 @@ __be32 in_aton(const char *str)
 	int i;
 
 	l = 0;
-	for (i = 0; i < 4; i++)
-	{
+	for (i = 0; i < 4; i++)	{
 		l <<= 8;
-		if (*str != '\0')
-		{
+		if (*str != '\0') {
 			val = 0;
-			while (*str != '\0' && *str != '.' && *str != '\n')
-			{
+			while (*str != '\0' && *str != '.' && *str != '\n') {
 				val *= 10;
 				val += *str - '0';
 				str++;
-- 
1.7.9


             reply	other threads:[~2012-04-08 16:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-08 16:07 Jeffrin Jose [this message]
2012-04-12 20:36 ` [PATCH] fixed coding style issue David Miller

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=20120408160742.GA4613@debian.Jeff \
    --to=ahiliation@yahoo.co.in \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.