From: Pavel Machek <pavel@ucw.cz>
To: Brian Swetland <swetland@google.com>
Cc: Arve Hj??nnev??g <arve@android.com>,
Daniel Walker <dwalker@codeaurora.org>,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Iliyan Malchev <malchev@google.com>, Greg KH <greg@kroah.com>
Subject: Re: tree with htc dream support
Date: Fri, 1 Jan 2010 15:54:51 +0100 [thread overview]
Message-ID: <20100101145451.GD3944@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <a55d774e0912281308u1c20c84cl4f264aa366445131@mail.gmail.com>
Hi!
(sorry for long response time, holidays with poor network connection).
> >> and get the core stuff in there so clock, power, etc support is there
> >> for the platform rather than have it live in staging purgatory.
> >>
> >> Since this stuff is integral to mach-msm, required for essential
> >> operation of the platform, and makes sense to be part of the mach-msm
> >> codebase, why not just fix it there rather than move it out into
> >> staging and then back? I'm not sure what that gains us.
> >
> > Well, it is in staging now. I just want you to use the existing
> > version, instead of adding another one.
>
> I'm trying to understand where the version in staging came from, how
> it's been changed, etc, so I can resolve that against what we have
> that's known good and shipping today and make sure we're not losing
> bugfixes and such along the way.
> Do you remember where the smd code that you put into staging came
> from, exactly? Unfortunately since things have been moved, modified,
> renamed, etc, getting clean diffs is a bit of an adventure right
> now.
I believe the version in staging is from 2.6.29-msm tree. Anyway,
changes should be pretty simple to see on diff -u (I belive I tried
that at one point).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2010-01-01 14:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 22:11 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
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 [this message]
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=20100101145451.GD3944@atrey.karlin.mff.cuni.cz \
--to=pavel@ucw.cz \
--cc=arve@android.com \
--cc=dwalker@codeaurora.org \
--cc=greg@kroah.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malchev@google.com \
--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
all inboxes | Powered by JetHome®