From: Amit Gud <amitg@calsoftinc.com>
To: linux-kernel@vger.kernel.org
Cc: kernel-janitors@lists.osdl.org, gud@eth.net
Subject: [KJ] [PATCH] Unified spinlock initialization include/linux/wait.h
Date: Tue, 25 Jan 2005 11:47:53 +0000 [thread overview]
Message-ID: <200501251705.58234.amitg@calsoftinc.com> (raw)
In-Reply-To: <20050120153602.GI25940@parcelfarce.linux.theplanet.co.uk>
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
Unify the spinlock initialization as far as possible.
Do consider applying.
Signed-off-by: Amit Gud <gud@eth.net>
--- orig/include/linux/wait.h 2005-01-20 20:06:42.000000000 +0530
+++ linux-2.6.11-rc2/include/linux/wait.h 2005-01-25 16:41:31.000000000 +0530
@@ -79,7 +79,7 @@ typedef struct __wait_queue_head wait_qu
static inline void init_waitqueue_head(wait_queue_head_t *q)
{
- q->lock = SPIN_LOCK_UNLOCKED;
+ spin_lock_init(&q->lock);
INIT_LIST_HEAD(&q->task_list);
}
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
WARNING: multiple messages have this Message-ID (diff)
From: Amit Gud <amitg@calsoftinc.com>
To: linux-kernel@vger.kernel.org
Cc: kernel-janitors@lists.osdl.org, gud@eth.net
Subject: [PATCH] Unified spinlock initialization include/linux/wait.h
Date: Tue, 25 Jan 2005 17:05:53 +0530 [thread overview]
Message-ID: <200501251705.58234.amitg@calsoftinc.com> (raw)
Unify the spinlock initialization as far as possible.
Do consider applying.
Signed-off-by: Amit Gud <gud@eth.net>
--- orig/include/linux/wait.h 2005-01-20 20:06:42.000000000 +0530
+++ linux-2.6.11-rc2/include/linux/wait.h 2005-01-25 16:41:31.000000000 +0530
@@ -79,7 +79,7 @@ typedef struct __wait_queue_head wait_qu
static inline void init_waitqueue_head(wait_queue_head_t *q)
{
- q->lock = SPIN_LOCK_UNLOCKED;
+ spin_lock_init(&q->lock);
INIT_LIST_HEAD(&q->task_list);
}
next parent reply other threads:[~2005-01-25 11:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 11:35 Amit Gud [this message]
2005-01-25 11:47 ` [KJ] [PATCH] Unified spinlock initialization include/linux/wait.h Amit Gud
-- strict thread matches above, loose matches on Subject: below --
2005-01-25 11:34 [PATCH] unified spinlock initialization arch/mips/kernel/irq.c Amit Gud
2005-01-25 11:46 ` [KJ] " Amit Gud
2005-01-25 13:43 ` [KJ] [PATCH] unified spinlock initialization Matthew Wilcox
2005-01-25 13:43 ` [KJ] [PATCH] unified spinlock initialization arch/mips/kernel/irq.c Matthew Wilcox
2005-01-20 15:36 [KJ] [PATCH] unified spinlock initialization Matthew Wilcox
2005-01-20 15:36 ` Amit Gud
2005-01-20 15:38 ` Amit Gud
2005-01-20 15:39 ` Amit Gud
2005-01-20 15:40 ` Amit Gud
2005-01-24 15:28 ` [KJ] [PATCH] unified spinlock initialization drivers/acpi/ec.c Amit Gud
2005-01-24 15:30 ` [KJ] [PATCH] unified spinlock initialization Amit Gud
2005-01-24 15:41 ` [KJ] [PATCH] unified spinlock initialization drivers/block/DAC960.c Amit Gud
2005-01-24 15:42 ` [KJ] [PATCH] unified spinlock initialization Amit Gud
2005-01-24 15:48 ` Amit Gud
2005-01-24 16:11 ` Randy.Dunlap
2005-01-24 16:25 ` Christophe Lucas
2005-01-24 16:41 ` Domen Puncer
2005-01-25 7:03 ` Christophe Lucas
2005-01-25 7:07 ` [KJ] [PATCH] Unified " Christophe Lucas
2005-01-25 11:33 ` Amit Gud
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=200501251705.58234.amitg@calsoftinc.com \
--to=amitg@calsoftinc.com \
--cc=gud@eth.net \
--cc=kernel-janitors@lists.osdl.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 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.