From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH v3 2/4] ARM: tegra: Add Harmony sound
	platform data type
Date: Fri, 21 Jan 2011 21:40:22 -0800
Message-ID: <AANLkTintANmyJBMdnLNTq_SRA9JoXOuqSv94xVYAPhUj@mail.gmail.com>
References: <1295393859-3396-1-git-send-email-swarren@wwwdotorg.org>
	<1295556731-25165-1-git-send-email-swarren@nvidia.com>
	<1295556731-25165-3-git-send-email-swarren@nvidia.com>
	<AANLkTimx3Co9HjpBoB07G8YnQG8LAukxMqLdCMgDf1j+@mail.gmail.com>
	<74CDBE0F657A3D45AFBB94109FB122FF03109559DF@HQMAIL01.nvidia.com>
	<AANLkTi=t0c4kCziPg=b0nqNRSw4od2U7__NwMu=dhW3Q@mail.gmail.com>
	<20110121234140.GA20247@opensource.wolfsonmicro.com>
	<74CDBE0F657A3D45AFBB94109FB122FF0310955A2F@HQMAIL01.nvidia.com>
	<AANLkTi=XQ7ATDOH8NDbXk4Fgs4D8rnDTR6LokExuo+gP@mail.gmail.com>
	<74CDBE0F657A3D45AFBB94109FB122FF0310955A8B@HQMAIL01.nvidia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <alsa-devel-bounces@alsa-project.org>
Received: from mail-fx0-f51.google.com (mail-fx0-f51.google.com
	[209.85.161.51]) by alsa0.perex.cz (Postfix) with ESMTP id 75F8324399
	for <alsa-devel@alsa-project.org>; Sat, 22 Jan 2011 06:40:22 +0100 (CET)
Received: by fxm5 with SMTP id 5so2533659fxm.38
	for <alsa-devel@alsa-project.org>; Fri, 21 Jan 2011 21:40:22 -0800 (PST)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF0310955A8B@HQMAIL01.nvidia.com>
List-Unsubscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
	<mailto:alsa-devel-request@alsa-project.org?subject=unsubscribe>
List-Archive: <http://mailman.alsa-project.org/pipermail/alsa-devel>
List-Post: <mailto:alsa-devel@alsa-project.org>
List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help>
List-Subscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
	<mailto:alsa-devel-request@alsa-project.org?subject=subscribe>
Sender: alsa-devel-bounces@alsa-project.org
Errors-To: alsa-devel-bounces@alsa-project.org
To: Stephen Warren <swarren@nvidia.com>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>, "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>, Mark Brown <broonie@opensource.wolfsonmicro.com>, Colin Cross <ccross@google.com>, "lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
List-Id: alsa-devel@alsa-project.org

On Fri, Jan 21, 2011 at 9:34 PM, Stephen Warren <swarren@nvidia.com> wrote:
> Olof Johansson wrote on Friday, January 21, 2011 10:15 PM:
>>
>> On Fri, Jan 21, 2011 at 3:49 PM, Stephen Warren wrote:
>> > Mark Brown wrote on Sent: Friday, January 21, 2011 4:42 PM:
>> >> The usual thing here would be a branch that gets merged into both trees
>> >> (to avoid the commit getting duplicated) or to only apply in one tree and
>> >> let things sort themselves out in -next and the merge window.
>> >
>> > Ah yes, I do remember you mentioning that before. Now I realize exactly
>> > what you mean.
>>
>> Sounds overly complicated to me since you don't already have a tree
>> hosted somewhere.
>
> Well, I did push a kernel repo to my personal server, which would do
> fine for this purpose assuming there's no requirement for it to stick
> around for any specific amount of time etc.


Ok, that works too :)


-Olof