From: <jes@trained-monkey.org>
To: alan@redhat.com
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: [patch] 64 bit bug in video1394.c
Date: Thu, 16 Aug 2001 00:53:19 -0400 [thread overview]
Message-ID: <200108160453.f7G4rJ219579@savage.trained-monkey.org> (raw)
Hi
More i2o 64 bit bugs.
Jes
--- drivers/message/i2o/i2o_config.c~ Wed Aug 8 00:08:04 2001
+++ drivers/message/i2o/i2o_config.c Thu Aug 16 00:50:28 2001
@@ -790,7 +790,7 @@
struct i2o_cfg_info *p = NULL;
struct i2o_evt_get *uget = (struct i2o_evt_get*)arg;
struct i2o_evt_get kget;
- unsigned int flags;
+ unsigned long flags;
for(p = open_files; p; p = p->next)
if(p->q_id == id)
@@ -819,7 +819,7 @@
{
struct i2o_cfg_info *tmp =
(struct i2o_cfg_info *)kmalloc(sizeof(struct i2o_cfg_info), GFP_KERNEL);
- unsigned int flags;
+ unsigned long flags;
if(!tmp)
return -ENOMEM;
@@ -845,7 +845,7 @@
{
u32 id = (u32)file->private_data;
struct i2o_cfg_info *p1, *p2;
- unsigned int flags;
+ unsigned long flags;
lock_kernel();
p1 = p2 = NULL;
--- drivers/message/i2o/i2o_core.c~ Wed Aug 8 00:08:04 2001
+++ drivers/message/i2o/i2o_core.c Thu Aug 16 00:51:26 2001
@@ -890,7 +890,7 @@
struct reply_info *reply = (struct reply_info *) reply_data;
u32 *msg = reply->msg;
struct i2o_controller *c = NULL;
- int flags;
+ unsigned long flags;
lock_kernel();
daemonize();
@@ -2535,7 +2535,7 @@
DECLARE_WAIT_QUEUE_HEAD(wq_i2o_post);
int complete = 0;
int status;
- int flags = 0;
+ unsigned long flags = 0;
struct i2o_post_wait_data *wait_data =
kmalloc(sizeof(struct i2o_post_wait_data), GFP_KERNEL);
next reply other threads:[~2001-08-16 4:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 4:53 jes [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-16 4:49 jes
2001-08-16 5:08 ` Jeff Chua
2001-08-16 4:47 jes
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=200108160453.f7G4rJ219579@savage.trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=alan@redhat.com \
--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®