From: blaisorblade@yahoo.it
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
blaisorblade@yahoo.it, domen@coderock.org, amitg@calsoftinc.com,
gud@eth.net
Subject: [patch 1/1] unified spinlock initialization arch/um/drivers/port_kern.c
Date: Wed, 09 Mar 2005 10:42:33 +0100 [thread overview]
Message-ID: <20050309094234.8FC0C6477@zion> (raw)
From: <domen@coderock.org>
Cc: <user-mode-linux-devel@lists.sourceforge.net>, <domen@coderock.org>, <amitg@calsoftinc.com>, <gud@eth.net>
Unify the spinlock initialization as far as possible.
Signed-off-by: Amit Gud <gud@eth.net>
Signed-off-by: Domen Puncer <domen@coderock.org>
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
---
linux-2.6.11-paolo/arch/um/drivers/port_kern.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN arch/um/drivers/port_kern.c~uml-switch-spinlock-init arch/um/drivers/port_kern.c
--- linux-2.6.11/arch/um/drivers/port_kern.c~uml-switch-spinlock-init 2005-03-09 10:35:28.786848080 +0100
+++ linux-2.6.11-paolo/arch/um/drivers/port_kern.c 2005-03-09 10:35:28.789847624 +0100
@@ -185,11 +185,11 @@ void *port_data(int port_num)
.has_connection = 0,
.sem = __SEMAPHORE_INITIALIZER(port->sem,
0),
- .lock = SPIN_LOCK_UNLOCKED,
.port = port_num,
.fd = fd,
.pending = LIST_HEAD_INIT(port->pending),
.connections = LIST_HEAD_INIT(port->connections) });
+ spin_lock_init(&port->lock);
list_add(&port->list, &ports);
found:
_
next reply other threads:[~2005-03-09 16:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 9:42 blaisorblade [this message]
2005-03-09 17:12 ` Russell King
2005-03-09 19:52 ` Blaisorblade
2005-03-09 22:42 ` Russell King
2005-03-09 22:50 ` Andrew Morton
2005-03-09 23:44 ` linux-os
2005-03-10 2:09 ` Zwane Mwaikambo
2005-03-10 8:12 ` Thomas Gleixner
2005-03-11 19:18 ` [uml-devel] " Blaisorblade
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=20050309094234.8FC0C6477@zion \
--to=blaisorblade@yahoo.it \
--cc=akpm@osdl.org \
--cc=amitg@calsoftinc.com \
--cc=domen@coderock.org \
--cc=gud@eth.net \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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®