public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Smart <jsmart2021@gmail.com>
To: Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH v3 00/16] lpfc: Add NVME Fabrics support
Date: Wed, 15 Feb 2017 08:04:54 -0800	[thread overview]
Message-ID: <bf3afee6-cd38-86fc-2e12-53df9c731987@gmail.com> (raw)
In-Reply-To: <3440afa9-9449-3378-6e8f-7cbe8dbb52cf@grimberg.me>



On 2/15/2017 2:12 AM, Sagi Grimberg wrote:
>
>>
>> The patches were cut against 1/30 scsi.git tree, misc branch.
>> ** THEY ARE INTENDED FOR THE SCSI.GIT TREE, MISC BRANCH **
>>
>> The lpfc version in the linux-block.git tree is rather old. I have a
>> recipe for how to get it to a version that syncs with the
>> scsi.git/misc tree so that these patches can apply there as well.
>> Contact me if you would like it.
>
> This set does not seem to apply cleanly on nvme-4.11 tree, looks
> like patch 6 is failing.

As I stated - the patches were cut vs the scsi.git tree - where the most 
recent lpfc is. So I expected merge via the scsi.git tree.

Given how old the scsi/lpfc part was on linux-block as of a little while 
ago, it doesn't surprise me they aren't clean.  I'll cut a version vs 
git.infradead.orig/nvme.git nvme-4.11 and send them privately.


>
> Also, can you send your patchset threaded? It usually does so
> when generating the patches with git format-patch, not sure
> how this is not the case with your set... It would make my
> life a bit easier.

Well, I am using git format-patch to create them. But have to revert to 
a manual mailing request as I haven't been able to get git-send-email 
working past our firewalls.  Sorry.

-- james

  reply	other threads:[~2017-02-15 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-12 21:52 [PATCH v3 00/16] lpfc: Add NVME Fabrics support James Smart
2017-02-15 10:12 ` Sagi Grimberg
2017-02-15 16:04   ` James Smart [this message]
2017-02-15 19:52     ` Bart Van Assche
2017-02-21  3:59 ` Martin K. Petersen

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=bf3afee6-cd38-86fc-2e12-53df9c731987@gmail.com \
    --to=jsmart2021@gmail.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sagi@grimberg.me \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox