From: Christoph Hellwig <hch@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: jbarnes@engr.sgi.com, erikj@subway.americas.sgi.com, pfg@sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6] Altix serial driver
Date: Fri, 25 Jun 2004 21:46:46 +0100 [thread overview]
Message-ID: <20040625204646.GA4343@infradead.org> (raw)
In-Reply-To: <20040625134537.072d17b9.akpm@osdl.org>
On Fri, Jun 25, 2004 at 01:45:37PM -0700, Andrew Morton wrote:
> I don't think we did that for /dev/kmsg.
>
> I haven't followed the politics or the history of this much, but if LANANA
> are being unresponsive and/or are ignoring 2.6 kernels, don't we need to
> either fix them up or route around them?
LANANA isn't ignoring 2.6. Linus mandated they shouldn't accept new
allocations for 2.6 anymore - but given there's very few 2.6-only drivers
this hasn't been much of a problem so far. Or to quote from
Documentation/devices.txt:
-------------------------------------------------------------------
THE DEVICE REGISTRY IS OFFICIALLY FROZEN FOR LINUS TORVALDS' KERNEL
TREE. At Linus' request, no more allocations will be made official
for Linus' kernel tree; the 3 June 2001 version of this list is the
official final version of this registry. At Alan Cox' request,
however, the registry will continue to be maintained for the -ac
series of kernels, and registrations will be accepted.
-------------------------------------------------------------------
next prev parent reply other threads:[~2004-06-25 20:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 14:48 [PATCH 2.6] Altix serial driver Pat Gefre
2004-06-23 15:06 ` Christoph Hellwig
2004-06-23 21:38 ` Andrew Morton
2004-06-23 21:54 ` Jesse Barnes
2004-06-25 3:15 ` Erik Jacobson
2004-06-25 8:31 ` Christoph Hellwig
2004-06-25 12:46 ` Erik Jacobson
2004-06-25 12:48 ` Christoph Hellwig
2004-06-25 13:00 ` Erik Jacobson
2004-06-26 23:52 ` Chris Wedgwood
2004-06-28 0:24 ` Erik Jacobson
2004-06-28 0:33 ` Chris Wedgwood
2004-06-28 1:14 ` Russell King
2004-06-28 1:44 ` Chris Wedgwood
2004-06-28 7:54 ` Russell King
2004-06-28 8:14 ` Chris Wedgwood
2004-06-28 9:02 ` Russell King
2004-06-28 12:28 ` Erik Jacobson
2004-06-28 19:04 ` Pat Gefre
2004-06-28 19:13 ` Andrew Morton
2004-06-28 19:47 ` Russell King
2004-06-28 20:57 ` Andrew Morton
2004-06-28 22:09 ` Pat Gefre
2004-06-28 22:20 ` Andrew Morton
2004-06-28 23:10 ` Russell King
2004-06-25 15:10 ` Jesse Barnes
2004-06-25 15:53 ` Christoph Hellwig
2004-06-25 20:45 ` Andrew Morton
2004-06-25 20:46 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-22 16:16 Pat Gefre
2004-06-22 18:24 ` Andrew Morton
2004-06-22 18:36 ` Christoph Hellwig
2004-06-23 14:42 ` Pat Gefre
2004-06-23 15:02 ` Christoph Hellwig
2004-06-23 15:07 ` Erik Jacobson
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=20040625204646.GA4343@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=erikj@subway.americas.sgi.com \
--cc=jbarnes@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pfg@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox