From: "Jordan Crouse" <jordan.crouse@amd.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: 2.6.19-rc5: Geode GX frame buffer takes 13 seconds to initialize
Date: Mon, 27 Nov 2006 14:07:41 -0700 [thread overview]
Message-ID: <20061127210741.GB5169@cosmic.amd.com> (raw)
In-Reply-To: <20061127123502.4253210c.akpm@osdl.org>
On 27/11/06 12:35 -0800, Andrew Morton wrote:
> It seems that there's duplication between Herbert's git-cryptodev tree
> and your git-geode tree.
>
> What's the story here?
Does - I'm an idiot count as an explanation? I committed the crime of
a duplicate commit (well, actually several crimes).
Go ahead and pull the tree from your list. I've decided to rebuild the
tree from scratch without the newbie behavior. I'll let you know when
its clean again.
Jordan
--
Jordan Crouse
Senior Linux Engineer
Advanced Micro Devices, Inc.
<www.amd.com/embeddedprocessors>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-11-27 21:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 16:29 2.6.19-rc5: Geode GX frame buffer takes 13 seconds to initialize Ben Gardner
2006-11-20 16:34 ` James Simmons
2006-11-20 22:47 ` Ben Gardner
2006-11-21 0:34 ` Jordan Crouse
2006-11-21 14:18 ` Ben Gardner
2006-11-27 16:28 ` Ben Gardner
2006-11-27 18:21 ` James Simmons
2006-11-27 18:39 ` Jordan Crouse
2006-11-27 19:54 ` Andrew Morton
2006-11-27 20:35 ` Andrew Morton
2006-11-27 21:07 ` Jordan Crouse [this message]
2006-11-27 18:36 ` Jordan Crouse
2006-11-21 15:07 ` James Simmons
2006-11-20 17:06 ` Jordan Crouse
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=20061127210741.GB5169@cosmic.amd.com \
--to=jordan.crouse@amd.com \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.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 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).