From: David Howells <dhowells@redhat.com>
To: "Brian J. Watson" <Brian.J.Watson@compaq.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] read/write semaphore trylock routines - 2.4.6
Date: Thu, 19 Jul 2001 08:41:43 +0100 [thread overview]
Message-ID: <2297.995528503@warthog.cambridge.redhat.com> (raw)
In-Reply-To: Message from "Brian J. Watson" <Brian.J.Watson@compaq.com> of "Wed, 18 Jul 2001 16:22:56 PDT." <3B561A50.A1B35FBC@compaq.com>
> Is this patch ready to go into the kernel? Is there anything else I
> should do to get it ready? I noticed it didn't make it into
> 2.4.7-pre7.
It looks reasonable, though I haven't tried it myself (I presume you have
though). You might want to try sending it direct to Linus.
David
next prev parent reply other threads:[~2001-07-19 7:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 3:32 [PATCH] read/write semaphore trylock routines - 2.4.6 Brian J. Watson
2001-07-10 7:32 ` David Howells
2001-07-11 3:20 ` Brian J. Watson
2001-07-18 23:22 ` Brian J. Watson
2001-07-19 7:41 ` David Howells [this message]
2001-07-25 17:56 ` [BUG 2.4.7] enabling RWSEM_DEBUG Brian J. Watson
2001-07-26 13:28 ` David Howells
2001-07-26 16:13 ` David Howells
2001-07-26 21:21 ` Brian J. Watson
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=2297.995528503@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=Brian.J.Watson@compaq.com \
--cc=linux-kernel@vger.kernel.org \
/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