From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bottomley Subject: Re: [PATCH 03/10] ide: destroy DMA mappings after ending DMA Date: Sat, 14 Mar 2009 15:50:16 -0500 Message-ID: <1237063816.3907.70.camel@localhost.localdomain> References: <20090220171139.25429.26702.sendpatchset@localhost.localdomain> <20090220171201.25429.29473.sendpatchset@localhost.localdomain> <200903142051.57971.bzolnier@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from accolon.hansenpartnership.com ([76.243.235.52]:41096 "EHLO accolon.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751793AbZCNUuU (ORCPT ); Sat, 14 Mar 2009 16:50:20 -0400 In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Grant Grundler Cc: Bartlomiej Zolnierkiewicz , linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org On Sat, 2009-03-14 at 21:45 +0100, Grant Grundler wrote: > On Sat, Mar 14, 2009 at 8:51 PM, Bartlomiej Zolnierkiewicz > wrote: > ... > >> I can create separate patches for both. Which git tree should I base > >> them against? > > > > linux-next git tree > > (or pata-2.6 quilt tree) > > I've not used quilt yet and can only deal with git in a very crude way. > Thanks for the references! Have no fear ... you just rsync the quilt to a directory (~/pata_quilt or something) on any server (use rsync so you only pick up the diffs next time around) and then do git quiltimport --patches ~/pata_quilt and voila: a git tree ... of course it's a new one, and it's much harder to handle incremental quilts (quilts that just have an extra few patches added) since git rebuilds the entire tree with a different commitid for each patch every time. James