linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: linux-kernel@vger.kernel.org,
	devfs-announce-list@vindaloo.ras.ucalgary.ca
Subject: [PATCH] devfs v181 available
Date: Mon, 18 Jun 2001 00:01:03 -0600	[thread overview]
Message-ID: <200106180601.f5I613D29992@vindaloo.ras.ucalgary.ca> (raw)

  Hi, all. Version 181 of my devfs patch is now available from:
http://www.atnf.csiro.au/~rgooch/linux/kernel-patches.html
The devfs FAQ is also available here.

Patch directly available from:
ftp://ftp.??.kernel.org/pub/linux/kernel/people/rgooch/v2.4/devfs-patch-current.gz

AND:
ftp://ftp.atnf.csiro.au/pub/people/rgooch/linux/kernel-patches/v2.4/devfs-patch-current.gz

This is against 2.4.6-pre3. Highlights of this release:

- Answered question posed by Al Viro and removed his comments from <devfs_open>

- Moved setting of registered flag after other fields are changed

- Fixed race between <devfsd_close> and <devfsd_notify_one>

- Global VFS changes added bogus BKL to devfsd_close(): removed

- Widened locking in <devfs_readlink> and <devfs_follow_link>

- Replaced <devfsd_read> stack usage with <devfsd_ioctl> kmalloc

- Simplified locking in <devfsd_ioctl> and fixed memory leak

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

             reply	other threads:[~2001-06-18  6:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-18  6:01 Richard Gooch [this message]
2001-06-18  6:33 ` [PATCH] devfs v181 available Alexander Viro
2001-06-18  6:40 ` Richard Gooch
2001-06-18  7:09   ` Alexander Viro
2001-06-18 15:15   ` Richard Gooch
2001-06-18 16:55     ` Alexander Viro
2001-06-18 18:53     ` Richard Gooch

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=200106180601.f5I613D29992@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=devfs-announce-list@vindaloo.ras.ucalgary.ca \
    --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;
as well as URLs for NNTP newsgroup(s).