From: Andrew Morton <akpm@osdl.org>
To: "Jordan Crouse" <jordan.crouse@amd.com>
Cc: linux-kernel@vger.kernel.org, blizzard@redhat.com,
dwmw2@redhat.com, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/2] OLPC + Geode fixups
Date: Tue, 25 Jul 2006 22:52:56 -0700 [thread overview]
Message-ID: <20060725225256.b4f98887.akpm@osdl.org> (raw)
In-Reply-To: <20060724165046.18787.23690.stgit@cosmic.amd.com>
On Mon, 24 Jul 2006 10:50:46 -0600
"Jordan Crouse" <jordan.crouse@amd.com> wrote:
> The following two patches are in support of the OLPC project. I sent these
> patches before, but somewhere along the line I failed to correctly follow up.
Actually I sneakily snuck
git://git.infradead.org/users/jcrouse/geode.git#linus-upstream into -mm (as
git-geode.patch) a month ago - it's been there since 2.6.17-mm3.
So assuming that tree is being kept up-to-date, I don't need to do
anything. Please arrange for the relevant subsystem maintainers to review
the bits of your tree which affect them (as you have done) and then send a
pull request to Linus at the appropriate time, cc'ing myself.
Unless there are significant bugfixes or this is a new subsystem, the
appropriate time would be in the post-2.6.18 two-week merge window.
And please let me know when there are -mm-affecting changes in that git tree.
Sometimes people add new branches without telling me, or they leave me
carrying abandoned stuff.
prev parent reply other threads:[~2006-07-26 5:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 16:50 Jordan Crouse
2006-07-24 16:53 ` [PATCH 1/2] GEODE: Update and fixup the PCI IDs for the CS5535 Jordan Crouse
2006-07-24 16:53 ` [PATCH 2/2] [PATCH] Add a configuration option to avoid automatically probing VGA Jordan Crouse
2006-07-26 5:52 ` Andrew Morton [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=20060725225256.b4f98887.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=blizzard@redhat.com \
--cc=dwmw2@redhat.com \
--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
all inboxes | Powered by JetHome®