From: Paul Mackerras <paulus@linuxcare.com>
To: linuxppc-dev@lists.linuxppc.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [linux-fbdev] Retrace
Date: Wed, 9 Feb 2000 13:45:15 +1100 [thread overview]
Message-ID: <00020913455600.26444@argo.linuxcare.com.au> (raw)
In-Reply-To: Pine.LNX.4.05.10002081101510.27293-100000@callisto.of.borg
On Tue, 08 Feb 2000, Geert Uytterhoeven wrote:
> Nope. But perhaps we should remove the #if !defined(CONFIG_PPC) around the
> port operations in drivers/char/mem.c?
Sounds like a good way to get machine checks to me. But then only root can
do it so maybe it doesn't matter.
Paul.
--
Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare. Support for the revolution.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-09 2:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-08 10:02 [linux-fbdev] Retrace Geert Uytterhoeven
2000-02-09 2:45 ` Paul Mackerras [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-02-09 13:45 Patrick Lerda
2000-02-09 14:09 ` Gabriel Paubert
2000-02-08 21:29 Benjamin Herrenschmidt
2000-02-09 9:57 ` Gabriel Paubert
2000-02-08 16:00 Andy
[not found] <Pine.LNX.4.10.10002071812050.1142-100000@cassiopeia.home>
2000-02-07 19:02 ` Benjamin Herrenschmidt
2000-02-08 9:29 ` Gabriel Paubert
2000-02-08 14:56 ` Benjamin Herrenschmidt
2000-02-08 16:47 ` Gabriel Paubert
2000-02-08 16:51 ` Geert Uytterhoeven
2000-02-08 17:09 ` Gabriel Paubert
2000-02-08 21:30 ` Benjamin Herrenschmidt
2000-02-08 21:39 ` Geert Uytterhoeven
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=00020913455600.26444@argo.linuxcare.com.au \
--to=paulus@linuxcare.com \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.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).