* Coding Style fixes
@ 2012-05-14 18:13 Jeffrin Jose
0 siblings, 0 replies; only message in thread
From: Jeffrin Jose @ 2012-05-14 18:13 UTC (permalink / raw)
To: oleg; +Cc: tj, akpm, serge.hallyn, matt.fleming, linux-kernel, ahiliation
[-- 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
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2012-05-14 18:10 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-14 18:13 Coding Style fixes Jeffrin Jose
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox