From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: radeonfb on linuxppc_2_4 tree ...
Date: 16 Jun 2003 19:11:06 +0200 [thread overview]
Message-ID: <1055783465.622.3.camel@gaston> (raw)
In-Reply-To: <20030616165534.GA6319@iliana>
On Mon, 2003-06-16 at 18:55, Sven Luther wrote:
> Hello,
>
> I am trying to build a linuxppc_2_4 bk tree checked out with the 2.4.21
> tag. But i get this error :
It's my fault ;)
Use the one in the linuxppc_2_4_benh tree at least until I fix linuxppc_2_4
Ben.
-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
prev parent reply other threads:[~2003-06-16 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 16:55 radeonfb on linuxppc_2_4 tree Sven Luther
2003-06-16 17:11 ` Benjamin Herrenschmidt [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=1055783465.622.3.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=sven.luther@wanadoo.fr \
/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).