From: Jianjun Kong <jianjun@zeuux.org>
To: Dotan Barak <dotanba@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [PATCH] kernel/workqueue.c mm/sparse.c: fix some linux coding style typos
Date: Sat, 18 Oct 2008 09:51:12 +0800 [thread overview]
Message-ID: <20081018015112.GA6861@ubuntu> (raw)
In-Reply-To: <200810180516.40060.dotanba@gmail.com>
On Sat, Oct 18, 2008 at 05:16:39AM +0200, Dotan Barak wrote:
>workqueues: fix some linux coding style typos:
>
>* spaces were replaced with tabs
>* "foo* bar" was replaced with "foo *bar"
>
>Signed-off-by: Dotan Barak <dotanba@gmail.com>
>
>---
>
>diff --git a/kernel/workqueue.c b/kernel/workqueue.c
>index 714afad..f9de8b5 100644
>--- a/kernel/workqueue.c
>+++ b/kernel/workqueue.c
>@@ -300,7 +300,7 @@ static void run_workqueue(struct cpu_workqueue_struct *cwq)
The same problem is in mm/sparse.c .
* spaces were replaced with tabs
* "foo* bar" was replaced with "foo *bar"
Signed-off-by: Dotan Barak <dotanba@gmail.com>
Signed-off-by: Jianjun Kong <jianjun@zeuux.org>
---
kernel/workqueue.c | 6 +++---
mm/sparse.c | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index 714afad..f9de8b5 100644
--- a/kernel/workqueue.c
+++ b/kernel/workqueue.c
@@ -300,7 +300,7 @@ static void run_workqueue(struct cpu_workqueue_struct *cwq)
printk(KERN_ERR "BUG: workqueue leaked lock or atomic: "
"%s/0x%08x/%d\n",
current->comm, preempt_count(),
- task_pid_nr(current));
+ task_pid_nr(current));
printk(KERN_ERR " last function: ");
print_symbol("%s\n", (unsigned long)f);
debug_show_held_locks(current);
@@ -551,7 +551,7 @@ static void wait_on_work(struct work_struct *work)
}
static int __cancel_work_timer(struct work_struct *work,
- struct timer_list* timer)
+ struct timer_list *timer)
{
int ret;
@@ -908,7 +908,7 @@ void destroy_workqueue(struct workqueue_struct *wq)
for_each_cpu_mask_nr(cpu, *cpu_map)
cleanup_workqueue_thread(per_cpu_ptr(wq->cpu_wq, cpu));
- cpu_maps_update_done();
+ cpu_maps_update_done();
free_percpu(wq->cpu_wq);
kfree(wq);
diff --git a/mm/sparse.c b/mm/sparse.c
index 39db301..47cb5c3 100644
--- a/mm/sparse.c
+++ b/mm/sparse.c
@@ -114,7 +114,7 @@ static inline int sparse_index_init(unsigned long section_nr, int nid)
* to also work for the flat array case because
* NR_SECTION_ROOTS==NR_MEM_SECTIONS.
*/
-int __section_nr(struct mem_section* ms)
+int __section_nr(struct mem_section *ms)
{
unsigned long root_nr;
struct mem_section* root;
--
1.5.2.5
--
Jianjun Kong | Happy Hacking
HomePage: http://kongove.cn
Gtalk: kongjianjun@gmail.com
prev parent reply other threads:[~2008-10-18 1:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 3:16 [PATCH] workqueues: fix some linux coding style typos Dotan Barak
2008-10-18 1:51 ` Jianjun Kong [this message]
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=20081018015112.GA6861@ubuntu \
--to=jianjun@zeuux.org \
--cc=akpm@linux-foundation.org \
--cc=dotanba@gmail.com \
--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 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.