From: John Heil <kerndev@sc-software.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] exclusive wakeup for lock_buffer
Date: Mon, 19 Feb 2001 19:28:37 +0000 ( ) [thread overview]
Message-ID: <Pine.LNX.3.95.1010219192656.8485A-100000@scsoftware.sc-software.com> (raw)
In-Reply-To: <E14V3Du-0005Py-00@the-village.bc.nu>
On Tue, 20 Feb 2001, Alan Cox wrote:
> Date: Tue, 20 Feb 2001 03:12:15 +0000 (GMT)
> From: Alan Cox <alan@lxorguk.ukuu.org.uk>
> To: Marcelo Tosatti <marcelo@conectiva.com.br>
> Cc: Linus Torvalds <torvalds@transmeta.com>,
> lkml <linux-kernel@vger.kernel.org>
> Subject: Re: [PATCH] exclusive wakeup for lock_buffer
>
> > --- linux/include/linux/locks.h.orig Mon Feb 19 23:16:50 2001
> > +++ linux/include/linux/locks.h Mon Feb 19 23:21:48 2001
> > @@ -13,6 +13,7 @@
> > * lock buffers.
> > */
> > extern void __wait_on_buffer(struct buffer_head *);
> > +extern void __lock_buffer(struct buffer_head *);
>
> So are we starting 2.5 now ?
If per chance it's so, what's actually in plan for 2.5 so far?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
-----------------------------------------------------------------
John Heil
South Coast Software
Custom systems software for UNIX and IBM MVS mainframes
1-714-774-6952
kerndev@sc-software.com
http://www.sc-software.com
-----------------------------------------------------------------
next prev parent reply other threads:[~2001-02-20 3:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 0:03 Marcelo Tosatti
2001-02-20 2:00 ` Linus Torvalds
2001-02-20 0:51 ` Marcelo Tosatti
2001-02-20 3:12 ` Alan Cox
2001-02-19 19:28 ` John Heil [this message]
2001-02-20 20:30 ` Marcelo Tosatti
2001-02-20 22:33 ` Alan Cox
2001-02-21 3:09 ` Ulf Carlsson
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=Pine.LNX.3.95.1010219192656.8485A-100000@scsoftware.sc-software.com \
--to=kerndev@sc-software.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®