From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754987AbZFYGiS (ORCPT ); Thu, 25 Jun 2009 02:38:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752224AbZFYGiF (ORCPT ); Thu, 25 Jun 2009 02:38:05 -0400 Received: from brick.kernel.dk ([93.163.65.50]:39872 "EHLO kernel.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751663AbZFYGiE (ORCPT ); Thu, 25 Jun 2009 02:38:04 -0400 Date: Thu, 25 Jun 2009 08:38:06 +0200 From: Jens Axboe To: Stephen Rothwell Cc: Alasdair G Kergon , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Christoph Hellwig , Al Viro Subject: Re: linux-next: manual merge of the block tree with Linus' tree Message-ID: <20090625063806.GC31415@kernel.dk> References: <20090625131517.d9adc935.sfr@canb.auug.org.au> <20090625133005.9f521529.sfr@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090625133005.9f521529.sfr@canb.auug.org.au> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 25 2009, Stephen Rothwell wrote: > On Thu, 25 Jun 2009 13:15:17 +1000 Stephen Rothwell wrote: > > > > I can't see how to easily fix this up, so I have dropped the block tree > > for today (since it only contained 2.6.32 material, right?). > > I also dropped the device-mapper tree for today as it was based on the > block tree (and dragged in what I had just dropped) and, in any case, all > its patches have been merged upstream. OK to both, I'm fixing up the writeback conflicts right now. -- Jens Axboe