From: Jianjun Kong <jianjun@zeuux.org>
To: cl@linux-foundation.org
Cc: Linux-Kernel-Mailing-List <linux-kernel@vger.kernel.org>
Subject: [PATCH] fork.c: fix a problem of code style
Date: Tue, 21 Oct 2008 22:16:47 +0800 [thread overview]
Message-ID: <20081021141647.GA12090@ubuntu> (raw)
fix a problem of code style
Signed-off-by: Jianjun Kong <jianjun@zeuux.org>
---
kernel/fork.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/fork.c b/kernel/fork.c
index 30de644..b6e5a94 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -187,7 +187,7 @@ void __init fork_init(unsigned long mempages)
/*
* we need to allow at least 20 threads to boot a system
*/
- if(max_threads < 20)
+ if (max_threads < 20)
max_threads = 20;
init_task.signal->rlim[RLIMIT_NPROC].rlim_cur = max_threads/2;
--
1.5.2.5
--
Jianjun Kong | Happy Hacking
HomePage: http://kongove.cn
Gtalk: kongjianjun@gmail.com
next reply other threads:[~2008-10-21 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 14:16 Jianjun Kong [this message]
2008-10-21 16:00 ` [PATCH] fork.c: fix a problem of code style Christoph Lameter
2008-10-21 16:32 ` David Newall
2008-10-29 0:28 ` Andrew Morton
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=20081021141647.GA12090@ubuntu \
--to=jianjun@zeuux.org \
--cc=cl@linux-foundation.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