From: Daniel Walker <dwalker@codeaurora.org>
To: Brian Swetland <swetland@google.com>
Cc: Pavel Machek <pavel@ucw.cz>, Arve Hj?nnev?g <arve@android.com>,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Iliyan Malchev <malchev@google.com>,
linux-kernel@codeaurora.org
Subject: Re: tree with htc dream support
Date: Sun, 06 Dec 2009 05:55:07 -0800 [thread overview]
Message-ID: <1260107707.23633.59.camel@desktop> (raw)
In-Reply-To: <a55d774e0912051638u7858878cg7cf62905c3c005c1@mail.gmail.com>
On Sat, 2009-12-05 at 16:38 -0800, Brian Swetland wrote:
> On Sat, Dec 5, 2009 at 3:12 PM, Daniel Walker <dwalker@codeaurora.org>
> wrote:
> https://www.codeaurora.org/gitweb/quic/kernel/?p=dwalker/linux-msm.git;a=shortlog;h=refs/heads/testing
>
> It's been in Linux-next for maybe two weeks .. I've been
> trying to
> decide if I should submit it for 2.6.33. I'm going to be
> adding boat
> loads of additional msm code and doing a fairly large merge
> for
> 2.6.34 .. So your code would get better testing if we wait for
> that.
>
> However, If you really want it in 2.6.33 I'll try to
> accommodate you.
>
> Arve's about to take our common and msm trees and rebase them over
> the .32, which may be useful for reference -- at least as a snapshot
> of a fully functional set of patches that android donut and eclair run
> on, on production hardware. We'll make that available as soon as we
> have something that's bootable.
Ok .. I'm mainly working with a small subset of a full Android tree.
It's just isolated to the arch/arm/mach-msm/ directory (some in
arch/arm/) .. If you guys have changes to that area just let me know
where they are and I'll try to move them forward.
Daniel
next prev parent reply other threads:[~2009-12-06 13:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 22:11 tree with htc dream support Pavel Machek
2009-12-05 23:12 ` Daniel Walker
2009-12-06 7:41 ` Pavel Machek
2009-12-06 13:51 ` Daniel Walker
2009-12-08 8:53 ` Pavel Machek
[not found] ` <a55d774e0912051638u7858878cg7cf62905c3c005c1@mail.gmail.com>
2009-12-06 7:43 ` Pavel Machek
2009-12-06 13:55 ` Daniel Walker [this message]
2009-12-12 5:42 ` Arve Hjønnevåg
2009-12-12 11:17 ` Pavel Machek
2009-12-12 11:25 ` Pavel Machek
2009-12-12 11:51 ` Arve Hjønnevåg
2009-12-12 12:11 ` Arve Hjønnevåg
2009-12-12 17:53 ` Pavel Machek
2009-12-12 22:41 ` Arve Hjønnevåg
2009-12-15 6:30 ` Arve Hjønnevåg
2009-12-12 14:18 ` Daniel Walker
2009-12-12 22:34 ` Arve Hjønnevåg
2009-12-13 21:25 ` Pavel Machek
2009-12-15 6:34 ` Arve Hjønnevåg
2009-12-15 22:20 ` Pavel Machek
2009-12-27 9:35 ` Pavel Machek
2009-12-27 20:15 ` Pavel Machek
2009-12-27 20:20 ` Brian Swetland
2009-12-27 20:37 ` Pavel Machek
2009-12-27 21:13 ` Pavel Machek
2009-12-27 21:53 ` Pavel Machek
2009-12-28 0:46 ` Brian Swetland
2009-12-27 10:18 ` Pavel Machek
2009-12-28 20:24 ` Brian Swetland
2009-12-28 20:48 ` Pavel Machek
2009-12-28 20:52 ` Pavel Machek
2009-12-28 21:08 ` Brian Swetland
2010-01-01 14:54 ` Pavel Machek
2009-12-29 1:25 ` Daniel Walker
2010-01-01 15:18 ` Pavel Machek
2010-01-01 16:08 ` Daniel Walker
2010-01-02 10:55 ` Pavel Machek
2010-01-05 21:31 ` Daniel Walker
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=1260107707.23633.59.camel@desktop \
--to=dwalker@codeaurora.org \
--cc=arve@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malchev@google.com \
--cc=pavel@ucw.cz \
--cc=swetland@google.com \
/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