[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a55d774e0912281224y7360dfdbu8a251743026bdd28@mail.gmail.com>
Date: Mon, 28 Dec 2009 12:24:20 -0800
From: Brian Swetland <swetland@...gle.com>
To: Pavel Machek <pavel@....cz>
Cc: "Arve Hj?nnev?g" <arve@...roid.com>,
Daniel Walker <dwalker@...eaurora.org>,
kernel list <linux-kernel@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Iliyan Malchev <malchev@...gle.com>,
linux-kernel@...eaurora.org, Greg KH <greg@...ah.com>
Subject: Re: tree with htc dream support
On Sun, Dec 27, 2009 at 2:18 AM, Pavel Machek <pavel@....cz> wrote:
> Hi!
>
>> > Switch smd code to the version in staging. Something to apply to
>> > dream/ tree I'd say... and yes, it still works.
>>
>> I think we might want to consider leaving at least the core smd code
>> under mach-msm.
>
> In the long run, I agree.
>
> In the short run... the code is staging quality, so it should be in
> staging... and you'll not have to mainain so huge diff. (-20 kLoc).
The core smd stuff is really not that large. The central smd.[ch] are
about 1300 lines, and proc_comm.[ch] are about 400 lines. Is it
possible to get some review/feedback as to what's "staging quality"
about this code so we can clean it up? I'd rather just fix the issues
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.
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