From: <jes@trained-monkey.org>
To: torvalds@transmeta.com
Cc: alan@redhat.com, linux-kernel@vger.kernel.org
Subject: [patch] dz.c 64 bit locking issues
Date: Thu, 16 Aug 2001 00:30:16 -0400 [thread overview]
Message-ID: <200108160430.f7G4UGT19451@savage.trained-monkey.org> (raw)
Hi
Another 64 bit flags bug.
Cheers
Jes
--- drivers/char/n_r3964.c~ Wed Jun 27 17:13:01 2001
+++ drivers/char/n_r3964.c Thu Aug 16 00:29:13 2001
@@ -1421,7 +1421,7 @@
int pid=current->pid;
struct r3964_client_info *pClient;
struct r3964_message *pMsg=NULL;
- unsigned int flags;
+ unsigned long flags;
int result = POLLOUT;
TRACE_L("POLL");
next reply other threads:[~2001-08-16 4:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 4:30 jes [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-16 4:26 [patch] dz.c 64 bit locking issues jes
2001-08-17 14:40 ` Ralf Baechle
2001-08-17 15:57 ` Maciej W. Rozycki
2001-08-17 15:59 ` Jes Sorensen
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=200108160430.f7G4UGT19451@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