From: David Miller <davem@davemloft.net>
To: mikpe@it.uu.se
Cc: adaplas@gmail.com, linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [PATCH 2.6.17 sparc64] 32-bit compat for Mach64 framebuffer
Date: Wed, 05 Jul 2006 20:52:33 -0700 (PDT) [thread overview]
Message-ID: <20060705.205233.39177061.davem@davemloft.net> (raw)
In-Reply-To: <200607060144.k661iH8d010317@harpo.it.uu.se>
From: Mikael Pettersson <mikpe@it.uu.se>
Date: Thu, 6 Jul 2006 03:44:17 +0200 (MEST)
> That could work. But it's a much larger patch than mine,
> and I don't want to go around hacking random other stuff
> just to repair atyfb. It's up the the Powers That Be to
> decide whether a local fix or a global one is most appropriate.
...
> That would require sbuslib.h to be completely benign on
> non-SPARC machines. If it is, great, but I can't currently
> guarantee that it is.
I've been aware of these warnings for a long time, but I've
done nothing about it because the fix is much worse than the
cure.
The is no reason the mach64 driver should be aware in any way
of these SBUS framebuffer ioctls.
Either we can find a way to make X stop issuing these ioctls
or simply ignore the kernel message, which frankly is harmless.
next prev parent reply other threads:[~2006-07-06 3:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 1:44 [PATCH 2.6.17 sparc64] 32-bit compat for Mach64 framebuffer Mikael Pettersson
2006-07-06 3:52 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-06 0:20 Mikael Pettersson
2006-07-06 1:01 ` Antonino A. Daplas
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=20060705.205233.39177061.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=sparclinux@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).