From: James Smart <jsmart2021@gmail.com>
To: Johannes Thumshirn <jthumshirn@suse.de>,
linux-nvme@lists.infradead.org, sagi@grimberg.me,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH v2 07/18] lpfc: NVME Initiator: Base modifications Part E
Date: Tue, 7 Feb 2017 18:32:30 -0800 [thread overview]
Message-ID: <52f4f81e-2353-4da2-7ce9-a7cd7796e1f7@gmail.com> (raw)
In-Reply-To: <5881e84b-c932-f812-7f41-a16152d12106@suse.de>
On 2/7/2017 1:03 AM, Johannes Thumshirn wrote:
>
> Yes but patch 03/18 'lpfc: NVME Initiator: Base modifications Part A'
> still has calls to lpfc_sli_hbq_count(phba) (and in fact introduces this
> change).
>
I realize I cut these in a silly way. In the v1 patches, I had a big
patch that I then cut into 6 parts, by file. In the v2 patches, I tried
to keep the patches as is, and address the comments in the respective
patch the comment came from. Which resulted in 3/8 with an old
reference, but patch 8/8 being the one that reverted this reverence.
Sorry.. I'll recut and repost.
-- james
WARNING: multiple messages have this Message-ID (diff)
From: jsmart2021@gmail.com (James Smart)
Subject: [PATCH v2 07/18] lpfc: NVME Initiator: Base modifications Part E
Date: Tue, 7 Feb 2017 18:32:30 -0800 [thread overview]
Message-ID: <52f4f81e-2353-4da2-7ce9-a7cd7796e1f7@gmail.com> (raw)
In-Reply-To: <5881e84b-c932-f812-7f41-a16152d12106@suse.de>
On 2/7/2017 1:03 AM, Johannes Thumshirn wrote:
>
> Yes but patch 03/18 'lpfc: NVME Initiator: Base modifications Part A'
> still has calls to lpfc_sli_hbq_count(phba) (and in fact introduces this
> change).
>
I realize I cut these in a silly way. In the v1 patches, I had a big
patch that I then cut into 6 parts, by file. In the v2 patches, I tried
to keep the patches as is, and address the comments in the respective
patch the comment came from. Which resulted in 3/8 with an old
reference, but patch 8/8 being the one that reverted this reverence.
Sorry.. I'll recut and repost.
-- james
next prev parent reply other threads:[~2017-02-08 2:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 23:08 [PATCH v2 07/18] lpfc: NVME Initiator: Base modifications Part E James Smart
2017-02-06 23:08 ` James Smart
2017-02-07 9:03 ` Johannes Thumshirn
2017-02-07 9:03 ` Johannes Thumshirn
2017-02-08 2:32 ` James Smart [this message]
2017-02-08 2:32 ` James Smart
2017-02-08 12:47 ` Christoph Hellwig
2017-02-08 12:47 ` Christoph Hellwig
2017-02-08 19:13 ` James Smart
2017-02-08 19:13 ` James Smart
2017-02-09 6:45 ` Hannes Reinecke
2017-02-09 6:45 ` Hannes Reinecke
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=52f4f81e-2353-4da2-7ce9-a7cd7796e1f7@gmail.com \
--to=jsmart2021@gmail.com \
--cc=jthumshirn@suse.de \
--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 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.