From: Adrian Bunk <bunk@stusta.de>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove mentionings of devfs in documentation
Date: Wed, 12 Jul 2006 02:36:06 +0200 [thread overview]
Message-ID: <20060712003606.GA32259@stusta.de> (raw)
In-Reply-To: <44B3C781.8060005@gmail.com>
On Tue, Jul 11, 2006 at 05:45:05PM +0200, Michal Piotrowski wrote:
> Hi Adrian,
>
> Adrian Bunk:
> > Now that devfs is removed, there's no longer any need to document how to
> > do this or that with devfs.
> >
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> >
> > ---
> [snip]
> > --- linux-2.6.18-rc1-mm1-full/Documentation/ABI/obsolete/devfs 2006-07-09 11:22:37.000000000 +0200
> > +++ /dev/null 2006-04-23 00:42:46.000000000 +0200
> > @@ -1,13 +0,0 @@
> > -What: devfs
> > -Date: July 2005
> > -Contact: Greg Kroah-Hartman <gregkh@suse.de>
> > -Description:
> > - devfs has been unmaintained for a number of years, has unfixable
> > - races, contains a naming policy within the kernel that is
> > - against the LSB, and can be replaced by using udev.
> > - The files fs/devfs/*, include/linux/devfs_fs*.h will be removed,
> > - along with the the assorted devfs function calls throughout the
> > - kernel tree.
> > -
> > -Users:
> > -
>
> According to Documentation/ABI/README
> " removed/
> This directory contains a list of the old interfaces that have
> been removed from the kernel.
> "
>
> we should add devfs to removed/
Thanks, agreed.
> Regards,
> Michal
>...
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2006-07-12 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 15:25 [2.6 patch] remove mentionings of devfs in documentation Adrian Bunk
2006-07-11 15:45 ` Michal Piotrowski
2006-07-12 0:36 ` Adrian Bunk [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=20060712003606.GA32259@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.