All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: martin@dalecki.de
Cc: Greg KH <greg@kroah.com>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org,
	rgooch@atnf.csiro.au
Subject: Re: [BK PATCH] devfs cleanups for 2.5.29
Date: Thu, 1 Aug 2002 11:57:01 +0200	[thread overview]
Message-ID: <20020801095701.GF1096@suse.de> (raw)
In-Reply-To: <3D4848D5.9080208@evision.ag>

On Wed, Jul 31 2002, Marcin Dalecki wrote:
> Greg KH wrote:
> >Hi,
> >
> >When devfs came alone, it created devfs_[un]register_chrdev and
> >devfs_[un]register_blkdev, which required that all drivers be changed to
> >be compatible with devfs. This change has been bothering a lot of people
> >for quite some time :)
> 
> Thanks! Finally someone got annoyed enough.

Yeah, let me add a big me too to that statement.

-- 
Jens Axboe


      reply	other threads:[~2002-08-01  9:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30 22:54 [BK PATCH] devfs cleanups for 2.5.29 Greg KH
2002-07-30 22:54 ` Greg KH
2002-07-30 22:55   ` Greg KH
2002-07-30 23:12 ` Richard Gooch
2002-07-30 23:18   ` Greg KH
2002-07-30 23:46     ` Greg KH
2002-07-30 23:35   ` Roman Zippel
2002-07-30 23:41     ` Richard Gooch
2002-07-31  0:31       ` Roman Zippel
2002-07-31  0:32         ` Richard Gooch
2002-07-31  9:32           ` Roman Zippel
2002-08-05 22:12             ` Richard Gooch
2002-08-05 22:48               ` Roman Zippel
2002-08-19  0:48                 ` Richard Gooch
2002-08-19  9:37                   ` Roman Zippel
2002-08-20 17:00                     ` Richard Gooch
2002-08-20 17:29                       ` Roman Zippel
2002-08-21  4:01                         ` Richard Gooch
2002-08-21 11:22                           ` Roman Zippel
2002-07-31 20:30 ` Marcin Dalecki
2002-08-01  9:57   ` Jens Axboe [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=20020801095701.GF1096@suse.de \
    --to=axboe@suse.de \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@dalecki.de \
    --cc=rgooch@atnf.csiro.au \
    --cc=torvalds@transmeta.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.