From: Jeffrin Jose <ahiliation@yahoo.co.in>
To: oleg@redhat.com
Cc: tj@kernel.org, akpm@linux-foundation.org,
serge.hallyn@canonical.com, matt.fleming@intel.com,
linux-kernel@vger.kernel.org, ahiliation@yahoo.co.in
Subject: Coding Style fixes
Date: Mon, 14 May 2012 23:43:10 +0530 [thread overview]
Message-ID: <20120514181310.GA29674@debian.Jeff> (raw)
[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]
hello ,
I have worked to fix coding style issues
relating to spaces in kernel/signal.c
>From 9bc77e7c5c6a5c8cefb0ed560a97ed3b2df3d269 Mon Sep 17 00:00:00 2001
From: Jeffrin Jose <ahiliation@yahoo.co.in>
Date: Mon, 14 May 2012 19:38:55 +0530
Subject: [PATCH] kernel:Coding Style Fixes in kernel/signal.c
Fixed coding style issues which includes ~ and &
operators in kernel/signal.c
Signed-off-by: Jeffrin Jose <ahiliation@yahoo.co.in>
---
kernel/signal.c | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
index d9bcff9..664df40 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -104,20 +104,20 @@ static inline int has_pending_signals(sigset_t *signal, sigset_t *blocked)
switch (_NSIG_WORDS) {
default:
for (i = _NSIG_WORDS, ready = 0; --i >= 0 ;)
- ready |= signal->sig[i] &~ blocked->sig[i];
+ ready |= signal->sig[i] & ~blocked->sig[i];
break;
- case 4: ready = signal->sig[3] &~ blocked->sig[3];
- ready |= signal->sig[2] &~ blocked->sig[2];
- ready |= signal->sig[1] &~ blocked->sig[1];
- ready |= signal->sig[0] &~ blocked->sig[0];
+ case 4: ready = signal->sig[3] & ~blocked->sig[3];
+ ready |= signal->sig[2] & ~blocked->sig[2];
+ ready |= signal->sig[1] & ~blocked->sig[1];
+ ready |= signal->sig[0] & ~blocked->sig[0];
break;
- case 2: ready = signal->sig[1] &~ blocked->sig[1];
- ready |= signal->sig[0] &~ blocked->sig[0];
+ case 2: ready = signal->sig[1] & ~blocked->sig[1];
+ ready |= signal->sig[0] & ~blocked->sig[0];
break;
- case 1: ready = signal->sig[0] &~ blocked->sig[0];
+ case 1: ready = signal->sig[0] & ~blocked->sig[0];
}
return ready != 0;
}
--
1.7.10
I have also added patch as attachment.
--
software engineer
Bohr Lab
department of computer science
Rajagiri school of engineering and technology.
[-- Attachment #2: 0001-kernel-Coding-Style-Fixes-in-kernel-signal.c.patch --]
[-- Type: text/x-diff, Size: 1617 bytes --]
>From 9bc77e7c5c6a5c8cefb0ed560a97ed3b2df3d269 Mon Sep 17 00:00:00 2001
From: Jeffrin Jose <ahiliation@yahoo.co.in>
Date: Mon, 14 May 2012 19:38:55 +0530
Subject: [PATCH] kernel:Coding Style Fixes in kernel/signal.c
Fixed coding style issues which includes ~ and &
operators in kernel/signal.c
Signed-off-by: Jeffrin Jose <ahiliation@yahoo.co.in>
---
kernel/signal.c | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
index d9bcff9..664df40 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -104,20 +104,20 @@ static inline int has_pending_signals(sigset_t *signal, sigset_t *blocked)
switch (_NSIG_WORDS) {
default:
for (i = _NSIG_WORDS, ready = 0; --i >= 0 ;)
- ready |= signal->sig[i] &~ blocked->sig[i];
+ ready |= signal->sig[i] & ~blocked->sig[i];
break;
- case 4: ready = signal->sig[3] &~ blocked->sig[3];
- ready |= signal->sig[2] &~ blocked->sig[2];
- ready |= signal->sig[1] &~ blocked->sig[1];
- ready |= signal->sig[0] &~ blocked->sig[0];
+ case 4: ready = signal->sig[3] & ~blocked->sig[3];
+ ready |= signal->sig[2] & ~blocked->sig[2];
+ ready |= signal->sig[1] & ~blocked->sig[1];
+ ready |= signal->sig[0] & ~blocked->sig[0];
break;
- case 2: ready = signal->sig[1] &~ blocked->sig[1];
- ready |= signal->sig[0] &~ blocked->sig[0];
+ case 2: ready = signal->sig[1] & ~blocked->sig[1];
+ ready |= signal->sig[0] & ~blocked->sig[0];
break;
- case 1: ready = signal->sig[0] &~ blocked->sig[0];
+ case 1: ready = signal->sig[0] & ~blocked->sig[0];
}
return ready != 0;
}
--
1.7.10
reply other threads:[~2012-05-14 18:10 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=20120514181310.GA29674@debian.Jeff \
--to=ahiliation@yahoo.co.in \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=oleg@redhat.com \
--cc=serge.hallyn@canonical.com \
--cc=tj@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.