Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751712AbZL1UYY (ORCPT ); Mon, 28 Dec 2009 15:24:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751638AbZL1UYY (ORCPT ); Mon, 28 Dec 2009 15:24:24 -0500 Received: from smtp-out.google.com ([216.239.44.51]:16275 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751583AbZL1UYX (ORCPT ); Mon, 28 Dec 2009 15:24:23 -0500 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=yaJZ4It3Q5cy4Mumgb46EcZRKUo7uL1EtxdUdNWXDofSrbSFWEX5B4ae+WekAIwY+ q+6dzAJ9eHMWwE7KWGtyQ== MIME-Version: 1.0 In-Reply-To: <20091227101824.GB1478@ucw.cz> References: <1260627482.20913.7.camel@desktop> <20091213212504.GD5114@elf.ucw.cz> <20091227093537.GD11737@elf.ucw.cz> <20091227201514.GA29174@elf.ucw.cz> <20091227203704.GK11737@elf.ucw.cz> <20091227211322.GB29174@elf.ucw.cz> <20091227101824.GB1478@ucw.cz> Date: Mon, 28 Dec 2009 12:24:20 -0800 Message-ID: Subject: Re: tree with htc dream support From: Brian Swetland To: Pavel Machek Cc: "Arve Hj?nnev?g" , Daniel Walker , kernel list , linux-arm-kernel , Iliyan Malchev , linux-kernel@codeaurora.org, Greg KH Content-Type: text/plain; charset=UTF-8 X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1385 Lines: 32 On Sun, Dec 27, 2009 at 2:18 AM, Pavel Machek 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/