From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andreas Theofilu <noreply@TheosSoft.net>
Cc: James Simmons <jsimmons@infradead.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: New FBDev patch
Date: Sat, 10 Jan 2004 01:10:53 +1100 [thread overview]
Message-ID: <1073657453.795.10.camel@gaston> (raw)
In-Reply-To: <20040109112733.EB14228003@chello062178157104.9.14.vie.surfer.at>
On Fri, 2004-01-09 at 22:27, Andreas Theofilu wrote:
> James Simmons wrote:
>
> >
> >
> > Try it again. I missed a patch for the radeon.
> >
> This is what happens here:
Looks like James cloned my tree right at the wrong time :)
This is fixed in the current one. In the meantime, change
"rom" with "rom_base"
Ben.
next prev parent reply other threads:[~2004-01-09 14:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1bRBM-5lD-13@gated-at.bofh.it>
[not found] ` <1bSRe-19C-21@gated-at.bofh.it>
2004-01-09 11:27 ` New FBDev patch Andreas Theofilu
2004-01-09 14:10 ` Benjamin Herrenschmidt [this message]
2004-06-23 18:04 New fbdev patch jsimmons
2004-06-25 14:11 ` Richard Smith
[not found] ` <20040629214850.GC2871@mercury.jahnsnet.de>
2004-06-29 22:27 ` Richard Smith
2004-06-30 16:57 ` jsimmons
2004-07-02 11:01 ` Thomas Jahns
2004-07-05 10:17 ` Thomas Jahns
-- strict thread matches above, loose matches on Subject: below --
2004-01-09 17:17 [Linux-fbdev-devel] New FBDev patch Kronos
2004-01-09 20:06 ` James Simmons
2004-01-08 22:03 James Simmons
2004-01-08 22:03 ` James Simmons
2004-01-08 22:56 ` Moritz Muehlenhoff
2004-01-08 23:05 ` Paul Mundt
2004-01-08 23:12 ` Tomas Szepe
2004-01-08 23:12 ` Tomas Szepe
2004-01-09 0:35 ` James Simmons
2004-01-09 0:35 ` James Simmons
2004-01-08 23:26 ` Russell King
2004-01-08 23:26 ` Russell King
2004-01-09 19:54 ` James Simmons
2004-01-09 19:54 ` James Simmons
2004-01-11 12:09 ` Russell King
2004-01-11 12:09 ` Russell King
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=1073657453.795.10.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noreply@TheosSoft.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.