From: Ralf Baechle <ralf@linux-mips.org>
To: Juan Quintela <quintela@mandrakesoft.com>
Cc: mipslist <linux-mips@linux-mips.org>
Subject: Re: [PATCH]: sgiserial 1/7: flags are unsigned long
Date: Thu, 27 Mar 2003 13:44:16 +0100 [thread overview]
Message-ID: <20030327134416.B26267@linux-mips.org> (raw)
In-Reply-To: <m2adfheczs.fsf@mandrakesoft.com>; from quintela@mandrakesoft.com on Thu, Mar 27, 2003 at 03:53:43AM +0100
On Thu, Mar 27, 2003 at 03:53:43AM +0100, Juan Quintela wrote:
> Subject: [PATCH]: sgiserial 1/7: flags are unsigned long
I applied the whole series of sgiserial patches.
I'm tired of maintaining the dead support for running IRIX's X server on
Linux. It was never working more than marginally and since Miguel de
Icaza has given up working on that in favor of Gnome the code is just a
maintenance pain. Worse, probably there's haven a dozen bad bugs hidden
in there allowing users to crash the system or do other sinister stuff.
So if you want to continue your cleanup cruzade by eleminating
drivers/sgi/ - I'm all for it :-)
Ralf
prev parent reply other threads:[~2003-03-27 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 2:53 [PATCH]: sgiserial 1/7: flags are unsigned long Juan Quintela
2003-03-27 12:44 ` Ralf Baechle [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=20030327134416.B26267@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=quintela@mandrakesoft.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