Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756213AbYF1MsS (ORCPT ); Sat, 28 Jun 2008 08:48:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752022AbYF1MsE (ORCPT ); Sat, 28 Jun 2008 08:48:04 -0400 Received: from smtpeu1.atmel.com ([195.65.72.27]:49515 "EHLO bagnes.atmel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751823AbYF1MsD (ORCPT ); Sat, 28 Jun 2008 08:48:03 -0400 Date: Sat, 28 Jun 2008 14:47:59 +0200 From: Haavard Skinnemoen To: Dan Williams Cc: Pierre Ossman , linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org, kernel@avr32linux.org, "Nelson, Shannon" , David Brownell Subject: Re: [PATCH v4 6/6] Atmel MCI: Driver for Atmel on-chip MMC controllers Message-ID: <20080628144759.2d9c7311@hskinnemo-gx745.norway.atmel.com> In-Reply-To: <1214602273.12666.7.camel@dwillia2-linux.ch.intel.com> References: <1214486603-23655-1-git-send-email-haavard.skinnemoen@atmel.com> <1214486603-23655-2-git-send-email-haavard.skinnemoen@atmel.com> <1214486603-23655-3-git-send-email-haavard.skinnemoen@atmel.com> <1214486603-23655-4-git-send-email-haavard.skinnemoen@atmel.com> <1214486603-23655-5-git-send-email-haavard.skinnemoen@atmel.com> <1214486603-23655-6-git-send-email-haavard.skinnemoen@atmel.com> <1214486603-23655-7-git-send-email-haavard.skinnemoen@atmel.com> <20080627211014.0e80db04@siona.local> <1214602273.12666.7.camel@dwillia2-linux.ch.intel.com> X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.9; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 28 Jun 2008 12:47:47.0384 (UTC) FILETIME=[2AB4F380:01C8D91D] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1016 Lines: 22 Dan Williams wrote: > > This driver has been out of tree for way too long. I'm hoping we can > > get it in before 2.6.27. > > I have high confidence that we can get the dma bits applied in time for > 2.6.27. You seem to have addressed my previous concerns and there has > been more than ample time for others with similar dma configurations to > comment on the dma-slave framework. I just want some more time to give > it an honest review. Sorry, I didn't mean to put pressure on you -- I certainly want an honest review. I meant it more as a sigh of relief that this troublesome driver is finally making its way into mainline...and that I can start working on preparing the other drivers that depend on the DMA slave interface. Haavard -- 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/