linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Greg KH <gregkh@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Patch series to remove devfs [00/22]
Date: Sat, 11 Jun 2005 16:41:07 +0100	[thread overview]
Message-ID: <20050611154107.GA32149@infradead.org> (raw)
In-Reply-To: <20050611153656.GB3770@stusta.de>

On Sat, Jun 11, 2005 at 05:36:56PM +0200, Adrian Bunk wrote:
> Yes, there are many places where 2.4 and 2.6 are not source compatible 
> for good reasons. But if the effort for maintaining compatibility 
> between 2.4 and 2.6 in one area is as easy as keeping a header file with 
> some dummy funtions it's worth considering.

The devfs calls for 2.4 and 2.6 are totally incompatible.  And there's
a trivial way to support both 2.4 and 2.6 in this area:  don't support
devfs at all, it always was marked either experimental or deprecated
anyway.


  reply	other threads:[~2005-06-11 15:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-11  7:43 [RFC] Patch series to remove devfs [00/22] Greg KH
2005-06-11 10:21 ` Adrian Bunk
2005-06-11 14:39   ` Greg KH
2005-06-11 15:36     ` Adrian Bunk
2005-06-11 15:41       ` Christoph Hellwig [this message]
2005-06-11 15:59         ` Adrian Bunk
2005-06-11 15:44       ` Kay Sievers
2005-06-11 20:14 ` [2.6 patch] fix compile errors and warning after devfs removal patches Adrian Bunk
2005-06-16 21:34   ` Greg KH
2005-06-12 22:44 ` [RFC] Patch series to remove devfs [00/22] J.A. Magallon
2005-06-13 17:43   ` Greg KH
2005-06-13 19:51     ` J.A. Magallon

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=20050611154107.GA32149@infradead.org \
    --to=hch@infradead.org \
    --cc=bunk@stusta.de \
    --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;
as well as URLs for NNTP newsgroup(s).