From: Ben Collins <bcollins@debian.org>
To: jes@trained-monkey.org
Cc: torvalds@transmeta.com, alan@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [patch] 64 bit locking in ieee1394/nodemgr.c
Date: Thu, 16 Aug 2001 01:11:57 -0400 [thread overview]
Message-ID: <20010816011157.B30381@visi.net> (raw)
In-Reply-To: <200108160439.f7G4d3b19502@savage.trained-monkey.org>
In-Reply-To: <200108160439.f7G4d3b19502@savage.trained-monkey.org>; from jes@trained-monkey.org on Thu, Aug 16, 2001 at 12:39:03AM -0400
On Thu, Aug 16, 2001 at 12:39:03AM -0400, jes@trained-monkey.org wrote:
> Hi
>
> The drivers/ieee1394/nodemgr.c driver tries to save cpu_flags in a 32
> bit type which is kinda bad.
Thanks. I'll apply all of the 1394 patches.
--
.----------=======-=-======-=========-----------=====------------=-=-----.
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` bcollins@debian.org -- bcollins@openldap.org -- bcollins@linux.com '
`---=========------=======-------------=-=-----=-===-======-------=--=---'
prev parent reply other threads:[~2001-08-16 5:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 4:39 [patch] 64 bit locking in ieee1394/nodemgr.c jes
2001-08-16 5:11 ` Ben Collins [this message]
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=20010816011157.B30381@visi.net \
--to=bcollins@debian.org \
--cc=alan@redhat.com \
--cc=jes@trained-monkey.org \
--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