All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: James Smart <james.smart@broadcom.com>
Cc: linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/3] nvme-fabrics: Add NVME FC Transport support to lpfc
Date: Thu, 11 Aug 2016 14:24:06 -0700	[thread overview]
Message-ID: <20160811212406.GI18013@infradead.org> (raw)
In-Reply-To: <5792b920.7v71BUERlAKN8sK4%james.smart@broadcom.com>

On Fri, Jul 22, 2016 at 05:24:00PM -0700, James Smart wrote:
> 
> This patchset adds NVME support to the lpfc FC driver.  It reworks
> the core driver for both NVME and SCSI protocol support, then adds the
> nvme-over-fabrics host and target interfaces which connect to the 
> NVME FC transport lower-level api.
> 
> Patches are cut against the linux-nvme for-4.8/drivers branch

Before reviewing the details:  what's the plan for merging this as we'll
have dependencies on both the SCSI and the block tree?

WARNING: multiple messages have this Message-ID (diff)
From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH 0/3] nvme-fabrics: Add NVME FC Transport support to lpfc
Date: Thu, 11 Aug 2016 14:24:06 -0700	[thread overview]
Message-ID: <20160811212406.GI18013@infradead.org> (raw)
In-Reply-To: <5792b920.7v71BUERlAKN8sK4%james.smart@broadcom.com>

On Fri, Jul 22, 2016@05:24:00PM -0700, James Smart wrote:
> 
> This patchset adds NVME support to the lpfc FC driver.  It reworks
> the core driver for both NVME and SCSI protocol support, then adds the
> nvme-over-fabrics host and target interfaces which connect to the 
> NVME FC transport lower-level api.
> 
> Patches are cut against the linux-nvme for-4.8/drivers branch

Before reviewing the details:  what's the plan for merging this as we'll
have dependencies on both the SCSI and the block tree?

  reply	other threads:[~2016-08-11 21:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-23  0:24 [PATCH 0/3] nvme-fabrics: Add NVME FC Transport support to lpfc James Smart
2016-07-23  0:24 ` James Smart
2016-08-11 21:24 ` Christoph Hellwig [this message]
2016-08-11 21:24   ` Christoph Hellwig
2016-08-22 17:41   ` James Smart
2016-08-22 17:41     ` James Smart

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=20160811212406.GI18013@infradead.org \
    --to=hch@infradead.org \
    --cc=james.smart@broadcom.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.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.