public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Armin Schindler <armin@melware.de>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Remove devfs_mk_cdev() function from the kernel tree
Date: Mon, 13 Jun 2005 11:13:23 -0700	[thread overview]
Message-ID: <20050613181323.GA13025@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0506121042420.30907@phoenix.one.melware.de>

On Sun, Jun 12, 2005 at 10:44:04AM +0200, Armin Schindler wrote:
> It didn't follow the development, is devfs now obsolete in kernel?
> If not, these funktions still makes sense.

I'm guessing you missed the [00/22] announcement of this patch?  Please
see that one for links to the issues surrounding this topic.

thanks,

greg k-h

  parent reply	other threads:[~2005-06-13 18:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11184761102127@kroah.com>
2005-06-11  7:48 ` [PATCH] Remove devfs from the partition code Greg KH
2005-06-11  7:48   ` [PATCH] Remove devfs from the init code Greg KH
2005-06-11  7:48     ` [PATCH] Remove devfs_*_tape() functions from the kernel tree Greg KH
2005-06-11  7:48       ` [PATCH] Remove devfs_mk_dir() function " Greg KH
2005-06-11  7:48         ` [PATCH] Remove devfs_mk_symlink() " Greg KH
2005-06-11  7:48           ` [PATCH] Remove devfs_mk_bdev() " Greg KH
2005-06-11  7:48             ` [PATCH] Remove devfs_mk_cdev() " Greg KH
2005-06-11  7:48               ` [PATCH] Remove devfs_remove() " Greg KH
2005-06-11  7:48                 ` [PATCH] Remove the devfs_fs_kernel.h file from the tree Greg KH
2005-06-11  7:48                   ` [PATCH] Remove the miscdevice devfs_name field as it's no longer needed Greg KH
2005-06-11  7:48                     ` [PATCH] Remove the gendisk " Greg KH
2005-06-11  7:48                       ` [PATCH] Remove the uart_driver " Greg KH
2005-06-11  7:48                         ` [PATCH] Remove the videodevice " Greg KH
2005-06-11  7:48                           ` [PATCH] Remove the ide drive " Greg KH
2005-06-11  7:48                             ` [PATCH] Remove the line_driver " Greg KH
2005-06-11  7:48                               ` [PATCH] Remove the scsi_disk " Greg KH
2005-06-11  7:48                                 ` [PATCH] Remove the tty_driver " Greg KH
2005-06-11  7:48                                   ` [PATCH] Remove the mode field from usb_class_driver " Greg KH
2005-06-11  7:48                                     ` [PATCH] Rename TTY_DRIVER_NO_DEVFS to TTY_DRIVER_DYNAMIC_DEV Greg KH
2005-06-11  7:48                                       ` [PATCH] Last little devfs cleanups throughout the kernel tree Greg KH
2005-06-11 19:05               ` [PATCH] Remove devfs_mk_cdev() function from " Adrian Bunk
2005-06-13 18:15                 ` Greg KH
2005-06-12  8:44               ` Armin Schindler
2005-06-12 13:29                 ` Ed Tomlinson
2005-06-12 13:51                   ` Armin Schindler
2005-06-12 15:12                     ` Adrian Bunk
2005-06-12 15:36                     ` Ed Tomlinson
2005-06-12 18:32                       ` Armin Schindler
2005-06-13 18:13                 ` Greg KH [this message]
2005-06-14  6:54                   ` Armin Schindler

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=20050613181323.GA13025@kroah.com \
    --to=gregkh@suse.de \
    --cc=armin@melware.de \
    --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