From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [patch 0/9] S3C24XX/S3C64XX updates Date: Wed, 11 Mar 2009 12:47:39 +0000 Message-ID: <20090311124738.GD20230@sirena.org.uk> References: <20090304004925.530566010@fluff.org.uk> <20090304202952.GA10731@sirena.org.uk> <20090305103111.GA2416@sirena.org.uk> <20090305110259.GC2416@sirena.org.uk> <20090311103936.GA18264@trinity.fluff.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from cassiel.sirena.org.uk (cassiel.sirena.org.uk [80.68.93.111]) by alsa0.perex.cz (Postfix) with ESMTP id 6FC7C2435D for ; Wed, 11 Mar 2009 13:47:42 +0100 (CET) Content-Disposition: inline In-Reply-To: <20090311103936.GA18264@trinity.fluff.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Ben Dooks Cc: Takashi Iwai , alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org On Wed, Mar 11, 2009 at 10:39:36AM +0000, Ben Dooks wrote: > At the moment this is still in your for-2.6.30 branch, do I need to look > at doing anything about it? I've pushed a revert of the two hunks I mentioned to Takashi already. If you could comment on the other two hunks I identified and provide a revert patch for them as well if they're not required that would be helpful - if they're not essential for this change they should be submitted separately via the ARM tree.