public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH] devfs: Remove the tty_driver devfs_name field as it's no longer needed
Date: Tue, 21 Jun 2005 00:18:14 -0700	[thread overview]
Message-ID: <20050621071814.GA15597@kroah.com> (raw)
In-Reply-To: <20050621080930.A30570@flint.arm.linux.org.uk>

On Tue, Jun 21, 2005 at 08:09:30AM +0100, Russell King wrote:
> On Mon, Jun 20, 2005 at 11:30:44PM -0700, Greg KH wrote:
> > [PATCH] devfs: Remove the tty_driver devfs_name field as it's no longer needed
> > 
> > Also fixes all drivers that set this field.
> 
> Except for:
> 
> drivers/serial/serial_core.c:   normal->devfs_name      = drv->devfs_name;

Was fixed in the patch entitled:
	Subject: devfs: Remove the uart_driver devfs_name field as it's no longer needed

which came earlier in this series, but probably hasn't made it out of
vger yet :)

thanks,

greg k-h

      reply	other threads:[~2005-06-21  8:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11193354424077@kroah.com>
2005-06-21  6:30 ` [PATCH] devfs: Remove devfs from the init code Greg KH
2005-06-21  6:30   ` [PATCH] devfs: Remove devfs_*_tape() functions from the kernel tree Greg KH
2005-06-21  6:30     ` [PATCH] devfs: Remove devfs_mk_symlink() function " Greg KH
2005-06-21  6:30       ` [PATCH] devfs: Remove devfs_mk_dir() " Greg KH
2005-06-21  6:30         ` [PATCH] devfs: Remove devfs_mk_bdev() " Greg KH
2005-06-21  6:30           ` [PATCH] devfs: Remove devfs_mk_cdev() " Greg KH
2005-06-21  6:30             ` [PATCH] devfs: Remove devfs_remove() " Greg KH
2005-06-21  6:30               ` [PATCH] devfs: Remove the miscdevice devfs_name field as it's no longer needed Greg KH
2005-06-21  6:30                 ` [PATCH] devfs: Remove the devfs_fs_kernel.h file from the tree Greg KH
2005-06-21  6:30                   ` [PATCH] devfs: Remove the uart_driver devfs_name field as it's no longer needed Greg KH
2005-06-21  6:30                     ` [PATCH] devfs: Remove the gendisk " Greg KH
2005-06-21  6:30                       ` [PATCH] devfs: Remove the videodevice " Greg KH
2005-06-21  6:30                         ` [PATCH] devfs: Remove the line_driver " Greg KH
2005-06-21  6:30                           ` [PATCH] devfs: Remove the ide drive " Greg KH
2005-06-21  6:30                             ` [PATCH] devfs: Remove the scsi_disk " Greg KH
2005-06-21  6:30                               ` [PATCH] devfs: Remove the tty_driver " Greg KH
2005-06-21  6:30                                 ` [PATCH] devfs: Remove the mode field from usb_class_driver " Greg KH
2005-06-21  6:30                                   ` [PATCH] devfs: Rename TTY_DRIVER_NO_DEVFS to TTY_DRIVER_DYNAMIC_DEV Greg KH
2005-06-21  6:30                                     ` [PATCH] devfs: Last little devfs cleanups throughout the kernel tree Greg KH
2005-06-21  8:12                                       ` Thomas Schneller
2005-06-21  7:09                                 ` [PATCH] devfs: Remove the tty_driver devfs_name field as it's no longer needed Russell King
2005-06-21  7:18                                   ` Greg KH [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=20050621071814.GA15597@kroah.com \
    --to=greg@kroah.com \
    --cc=gregkh@suse.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