From: devesh.pradhan1@gmail.com
To: viro@zeniv.linux.org.uk
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
devesh pradhan <devesh.pradhan1@gmail.com>
Subject: [PATCH 2/2] kernel: compat: fixed a trailing whitespaces code style issue
Date: Sun, 4 Feb 2018 10:57:32 +0530 [thread overview]
Message-ID: <20180204052732.3538-1-devesh.pradhan1@gmail.com> (raw)
From: devesh pradhan <devesh.pradhan1@gmail.com>
Fixed a coding style issue.
Signed-off-by: devesh pradhan <devesh.pradhan1@gmail.com>
---
kernel/compat.c | 24 ++++++++++++++++--------
1 file changed, 16 insertions(+), 8 deletions(-)
diff --git a/kernel/compat.c b/kernel/compat.c
index d1cee656a7ed..d40c83792ae9 100644
--- a/kernel/compat.c
+++ b/kernel/compat.c
@@ -475,10 +475,14 @@ get_compat_sigset(sigset_t *set, const compat_sigset_t __user *compat)
if (copy_from_user(&v, compat, sizeof(compat_sigset_t)))
return -EFAULT;
switch (_NSIG_WORDS) {
- case 4: set->sig[3] = v.sig[6] | (((long)v.sig[7]) << 32 );
- case 3: set->sig[2] = v.sig[4] | (((long)v.sig[5]) << 32 );
- case 2: set->sig[1] = v.sig[2] | (((long)v.sig[3]) << 32 );
- case 1: set->sig[0] = v.sig[0] | (((long)v.sig[1]) << 32 );
+ case 4:
+ set->sig[3] = v.sig[6] | (((long)v.sig[7]) << 32);
+ case 3:
+ set->sig[2] = v.sig[4] | (((long)v.sig[5]) << 32);
+ case 2:
+ set->sig[1] = v.sig[2] | (((long)v.sig[3]) << 32);
+ case 1:
+ set->sig[0] = v.sig[0] | (((long)v.sig[1]) << 32);
}
#else
if (copy_from_user(set, compat, sizeof(compat_sigset_t)))
@@ -496,10 +500,14 @@ put_compat_sigset(compat_sigset_t __user *compat, const sigset_t *set,
#ifdef __BIG_ENDIAN
compat_sigset_t v;
switch (_NSIG_WORDS) {
- case 4: v.sig[7] = (set->sig[3] >> 32); v.sig[6] = set->sig[3];
- case 3: v.sig[5] = (set->sig[2] >> 32); v.sig[4] = set->sig[2];
- case 2: v.sig[3] = (set->sig[1] >> 32); v.sig[2] = set->sig[1];
- case 1: v.sig[1] = (set->sig[0] >> 32); v.sig[0] = set->sig[0];
+ case 4:
+ v.sig[7] = (set->sig[3] >> 32); v.sig[6] = set->sig[3];
+ case 3:
+ v.sig[5] = (set->sig[2] >> 32); v.sig[4] = set->sig[2];
+ case 2:
+ v.sig[3] = (set->sig[1] >> 32); v.sig[2] = set->sig[1];
+ case 1:
+ v.sig[1] = (set->sig[0] >> 32); v.sig[0] = set->sig[0];
}
return copy_to_user(compat, &v, size) ? -EFAULT : 0;
#else
--
2.14.1
reply other threads:[~2018-02-04 5:27 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=20180204052732.3538-1-devesh.pradhan1@gmail.com \
--to=devesh.pradhan1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®