Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758691Ab0DPRNO (ORCPT ); Fri, 16 Apr 2010 13:13:14 -0400 Received: from mga10.intel.com ([192.55.52.92]:50401 "EHLO fmsmga102.fm.intel.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1758679Ab0DPRNK (ORCPT ); Fri, 16 Apr 2010 13:13:10 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.52,220,1270450800"; d="scan'208";a="558613315" Date: Fri, 16 Apr 2010 19:13:36 +0200 From: Samuel Ortiz To: Richard =?iso-8859-1?Q?R=F6jfors?= Cc: Linux Kernel Mailing List , Linux Media Mailing List , Mauro Carvalho Chehab , Douglas Schilling Landgraf , "Williams, Dan J" Subject: Re: [PATCH 0/2] media, mfd: Add timberdale video-in driver Message-ID: <20100416171335.GC28863@sortiz.org> References: <1271435274.11641.44.camel@debian> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1271435274.11641.44.camel@debian> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 947 Lines: 33 Hi Richard, On Fri, Apr 16, 2010 at 06:27:54PM +0200, Richard R?jfors wrote: > To follow are two patches. > > The first one adds the timberdale video-in driver to the media tree. > > The second one adds it to the timberdale MFD driver. > > The Kconfig of the media patch selects TIMB_DMA which is introduced > in the DMA tree, that's why I cc:d in Dan. > > Samuel and Mauro hope you can support and solve the potential merge > issue between your two trees. Mauro, the mfd part of this patch depends on the video one. Do you mind if I take both through my tree, after getting your Acked-by ? Cheers, Samuel. > Thanks > --Richard > -- Intel Open Source Technology Centre http://oss.intel.com/ -- 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/