From: Ben Collins <bcollins@debian.org>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: andreas.bombe@munich.netsurf.de,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove BKL from ieee1394_core release function
Date: Fri, 5 Apr 2002 15:10:58 -0500 [thread overview]
Message-ID: <20020405201058.GP29054@blimpo.internal.net> (raw)
In-Reply-To: <3CADF6E0.6060402@us.ibm.com>
On Fri, Apr 05, 2002 at 11:11:28AM -0800, Dave Hansen wrote:
> I produced a similar patch for 2.5 which I discussed on the ieee1394
> mailing list a few weeks ago. We decided that this was a safe and
> BKL-free approach. Here is a patch to do the same thing for 2.4.19-pre6.
Just let me put this into the linux1394 repo, and I'll forward the patch
to Marcello and Linus. Keeps me from having to track 3 sets of changes.
--
Debian - http://www.debian.org/
Linux 1394 - http://linux1394.sourceforge.net/
Subversion - http://subversion.tigris.org/
prev parent reply other threads:[~2002-04-05 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 19:11 [PATCH] remove BKL from ieee1394_core release function Dave Hansen
2002-04-05 20:10 ` 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=20020405201058.GP29054@blimpo.internal.net \
--to=bcollins@debian.org \
--cc=andreas.bombe@munich.netsurf.de \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-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