From: Andries.Brouwer@cwi.nl
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] compilation fix: spin_lock_irqsave uses unsigned long
Date: Sun, 20 Apr 2003 20:25:47 +0200 (MEST) [thread overview]
Message-ID: <UTC200304201825.h3KIPlr18093.aeb@smtp.cwi.nl> (raw)
diff -u --recursive --new-file -X /linux/dontdiff a/drivers/block/paride/pcd.c b/drivers/block/paride/pcd.c
--- a/drivers/block/paride/pcd.c Tue Apr 8 09:36:36 2003
+++ b/drivers/block/paride/pcd.c Sun Apr 20 19:55:24 2003
@@ -761,7 +761,7 @@
static inline void next_request(int success)
{
- long saved_flags;
+ unsigned long saved_flags;
spin_lock_irqsave(&pcd_lock, saved_flags);
end_request(pcd_req, success);
diff -u --recursive --new-file -X /linux/dontdiff a/drivers/block/paride/pd.c b/drivers/block/paride/pd.c
--- a/drivers/block/paride/pd.c Tue Apr 8 09:36:36 2003
+++ b/drivers/block/paride/pd.c Sun Apr 20 19:54:47 2003
@@ -757,7 +757,7 @@
static int pd_next_buf(void)
{
- long saved_flags;
+ unsigned long saved_flags;
pd_count--;
pd_run--;
@@ -777,7 +777,7 @@
static inline void next_request(int success)
{
- long saved_flags;
+ unsigned long saved_flags;
spin_lock_irqsave(&pd_lock, saved_flags);
end_request(pd_req, success);
diff -u --recursive --new-file -X /linux/dontdiff a/drivers/block/paride/pf.c b/drivers/block/paride/pf.c
--- a/drivers/block/paride/pf.c Sun Apr 20 12:59:31 2003
+++ b/drivers/block/paride/pf.c Sun Apr 20 19:57:04 2003
@@ -812,7 +812,7 @@
static int pf_next_buf(void)
{
- long saved_flags;
+ unsigned long saved_flags;
pf_count--;
pf_run--;
@@ -832,7 +832,8 @@
static inline void next_request(int success)
{
- long saved_flags;
+ unsigned long saved_flags;
+
spin_lock_irqsave(&pf_spin_lock, saved_flags);
end_request(pf_req, success);
pf_busy = 0;
reply other threads:[~2003-04-20 18:13 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=UTC200304201825.h3KIPlr18093.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®