From: Jeff Garzik <jeff@garzik.org>
To: Jordan Crouse <jordan.crouse@amd.com>
Cc: linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net, akpm@osdl.org
Subject: Re: [GIT PATCH] Geode patches for 2.6.17
Date: Fri, 23 Jun 2006 16:25:32 -0400 [thread overview]
Message-ID: <449C4E3C.7000107@garzik.org> (raw)
In-Reply-To: <20060623170058.GA12819@cosmic.amd.com>
Jordan Crouse wrote:
> Hi -
>
> Please consider pulling from:
> git://git.infradead.net/users/jcrouse/geode.git linus-upstream
>
> This is the new home for patches for the AMD Geode family of processors.
>
> For 2.6.18, we offer up patches to support the One Laptop
> Per Child effort - namely framebuffer tweaks, plus an attempt to remove
> automagic probing of VGA registers (which we don't have on the OLPC
> platform).
>
> Here is the shortlog:
>
> Jordan Crouse:
> GEODE: Update and fixup the PCI IDs for the CS5535
> FB: Get the Geode GX frambuffer size from the BIOS
> Add a configuration option to avoid automatically probing VGA
> gxfb: Fixups for the AMD Geode GX framebuffer driver
When you send a 'please pull' message, two additional things are needed:
* output of 'diffstat -p1'
* the patches themselves, either in this email, or spread out across
several emails in the same email thread (linked together with RFC822
References header)
Jeff
next prev parent reply other threads:[~2006-06-23 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 17:00 [GIT PATCH] Geode patches for 2.6.17 Jordan Crouse
2006-06-23 18:41 ` Alan Cox
2006-06-23 21:07 ` Jordan Crouse
2006-06-23 20:25 ` Jeff Garzik [this message]
2006-06-23 20:56 ` Jordan Crouse
2006-06-23 21:19 ` Alan Cox
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=449C4E3C.7000107@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=jordan.crouse@amd.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@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).