From: Geert Uytterhoeven <geert@linux-m68k.org>
To: David Miller <davem@davemloft.net>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fbdev@vger.kernel.org
Subject: Re: [GIT]: Sparc
Date: Sun, 14 Mar 2010 14:34:03 +0000 [thread overview]
Message-ID: <10f740e81003140734p30959952ld4563d2b22d834af@mail.gmail.com> (raw)
In-Reply-To: <20100313.181754.107699673.davem@davemloft.net>
Hi David,
On Sun, Mar 14, 2010 at 03:17, David Miller <davem@davemloft.net> wrote:
> David S. Miller (1):
> sparc64: Add very basic XVR-1000 framebuffer driver.
Have you ever looked into getting offb to work on sparc64?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next parent reply other threads:[~2010-03-14 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100313.181754.107699673.davem@davemloft.net>
2010-03-14 14:34 ` Geert Uytterhoeven [this message]
2010-03-14 21:24 ` [GIT]: Sparc David Miller
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=10f740e81003140734p30959952ld4563d2b22d834af@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=davem@davemloft.net \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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