All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Boaz Harrosh <bharrosh@panasas.com>, Tejun Heo <tj@kernel.org>,
	James Smart <James.Smart@Emulex.Com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	FUJITA Tomonori <tomof@acm.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH version 2] [SQUASHME] "FC Pass Thru support" fixed for block/for-2.6.31 tree
Date: Wed, 20 May 2009 21:10:16 +0200	[thread overview]
Message-ID: <20090520191016.GC11363@kernel.dk> (raw)
In-Reply-To: <1242830240.2881.10.camel@localhost.localdomain>

On Wed, May 20 2009, James Bottomley wrote:
> On Wed, 2009-05-20 at 11:16 +1000, Stephen Rothwell wrote:
> > On Tue, 19 May 2009 15:54:59 +0300 Boaz Harrosh <bharrosh@panasas.com> wrote:
> > >
> > > 
> > > This patch should be squashed into
> > >     [SCSI] FC Pass Thru support
> > > 
> > > If it needs to compile after Tejun's block-layer revamps
> > > (all of them)
> > 
> > Is there some reason that the FC passthrough support (and any followup
> > patches) can't be pushed through the block tree.  It clearly currently
> > doesn't depend on anything new in the scsi tree ...
> 
> That would preserve the logical sequence of patches, yes.  However, Jens
> is a bit pressed for time, so I agreed to do this in SCSI.
> 
> Unfortuantely, I still need the block tree for-next to be rebased up to
> the current linus head because of a couple of conflicts:
> 
> CONFLICT (content): Merge conflict in drivers/block/hd.c
> CONFLICT (content): Merge conflict in drivers/block/mg_disk.c
> 
> The are both just rebase/rebase conflicts:  it looks like there are two
> commit ids for 

James, I'll get this fixed (either pull linus tree in or rebase) and
send you a note! It wont be before tomorrow, I think.

-- 
Jens Axboe


  parent reply	other threads:[~2009-05-20 19:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19  9:18 [PATCH] [SQUASHME] "FC Pass Thru support" fixed for block/for-2.6.31 tree Boaz Harrosh
2009-05-19  9:18 ` Boaz Harrosh
2009-05-19 10:05 ` Tejun Heo
2009-05-19 10:14   ` Boaz Harrosh
2009-05-19 12:54 ` [PATCH version 2] " Boaz Harrosh
2009-05-19 12:54   ` Boaz Harrosh
2009-05-20  1:16   ` Stephen Rothwell
2009-05-20  8:11     ` Boaz Harrosh
2009-05-20 12:54       ` James Smart
2009-05-20 14:37     ` James Bottomley
2009-05-20 14:42       ` Stephen Rothwell
2009-05-20 14:47         ` James Bottomley
2009-05-20 16:20           ` James Bottomley
2009-05-20 16:39             ` Boaz Harrosh
2009-05-20 16:40               ` Boaz Harrosh
2009-05-20 16:43               ` James Bottomley
2009-05-20 16:59                 ` Boaz Harrosh
2009-05-20 17:03                   ` Boaz Harrosh
2009-05-20 17:11             ` James Bottomley
2009-05-20 14:45       ` Stephen Rothwell
2009-05-20 19:10       ` Jens Axboe [this message]
2009-05-20  4:16   ` Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090520191016.GC11363@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=James.Smart@Emulex.Com \
    --cc=bharrosh@panasas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tj@kernel.org \
    --cc=tomof@acm.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.