[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a55d774e0906241605u1e7aa816n823aad517f05a1e1@mail.gmail.com>
Date: Wed, 24 Jun 2009 16:05:42 -0700
From: Brian Swetland <swetland@...gle.com>
To: Daniel Walker <dwalker@...o99.com>
Cc: Arve Hjønnevåg <arve@...roid.com>,
Jeremy Fitzhardinge <jeremy@...p.org>,
Greg Kroah-Hartman <greg@...ah.com>,
linux-kernel@...r.kernel.org, hackbod@...roid.com
Subject: Re: [PATCH 1/6] staging: android: binder: Remove some funny && usage
On Wed, Jun 24, 2009 at 3:49 PM, Daniel Walker<dwalker@...o99.com> wrote:
>> For example the msm7k SoC code may need some various cleanup, but I
>> think at the end of the day adding support for a new ARM based SoC and
>> peripherals is not going to be that contentious. The
>> wakelock/suspendblock stuff is a bit further out there, but there
>> seemed to be some good progress on getting it reviewed and revised on
>> the linux-pm list, last I saw.
>
> Do you have a msm branch someplace that is strictly msm support with
> absolutely no generic changes mixed in?
Unfortunately, no. However, the generic changes tend to be
self-contained (binder, logger, etc) and not necessary for core msm7k
support. The one set of changes that does touch both generic and
platform code is the wakelock/suspendblock stuff, which some of the
drivers make use of, but that's usually not very invasive.
http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.29
is the most up to date msm7k tree.
We'll be rebasing on a newer kernel baseline in the near future (.29
is obviously not the cutting edge, but is what's being supported for
the upcoming donut release of the android platform).
Brian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists