From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Linux 2.4.17-pre6 drm-4.0
Date: Fri, 14 Dec 2001 19:13:15 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805696@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805654@msgid-missing>
>>>>> On Sat, 8 Dec 2001 13:31:56 +0100, Christoph Hellwig <hch@caldera.de> said:
Christoph> David, would you remove drm-4.0 from the ia64 patch if I'd do the work
Christoph> again and package an up-to-date and ia64-capable drm 4.0 out-of-tree?
In my opinion it's extremely bad style to remove drm-4.0 from the 2.4
kernel (remember, it's supposed to be a *stable* kernel series). As
far as I know, there are binary-only drivers out there that work only
with drm-4.0. I don't think it's fair to break someones working setup
just because of a kernel upgrade.
But if there is a good reason to remove it, I'm certainly willing to
listen. My understanding is that for Keith it's good enough if
drm-4.0 goes away in 2.5.
--david
next prev parent reply other threads:[~2001-12-14 19:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 23:27 [Linux-ia64] Re: Linux 2.4.17-pre6 drm-4.0 Robert Love
2001-12-07 23:32 ` Keith Owens
2001-12-07 23:42 ` Robert Love
2001-12-08 0:12 ` Barry K. Nathan
2001-12-08 11:35 ` Alan Cox
2001-12-08 11:35 ` Alan Cox
2001-12-08 12:31 ` Christoph Hellwig
2001-12-08 15:34 ` Alan Cox
2001-12-09 16:42 ` Christoph Hellwig
2001-12-14 19:13 ` David Mosberger [this message]
2001-12-15 10:19 ` Christoph Hellwig
2001-12-17 16:14 ` Marcelo Tosatti
2001-12-17 22:46 ` Juan Quintela
-- strict thread matches above, loose matches on Subject: below --
2001-12-07 23:20 Keith Owens
2001-12-08 11:35 ` Alan Cox
2001-12-08 12:31 ` [Linux-ia64] " Christoph Hellwig
2001-12-08 15:34 ` Alan Cox
2001-12-09 16:42 ` Christoph Hellwig
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=marc-linux-ia64-105590698805696@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@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 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.