From: Christoph Hellwig <hch@infradead.org>
To: jsmart2021@gmail.com
Cc: linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org,
sagi@grimberg.me, emilne@redhat.com, jthumshirn@suse.de,
linux-block@vger.kernel.org, martin.petersen@oracle.com,
Dick Kennedy <dick.kennedy@broadcom.com>,
James Smart <james.smart@broadcom.com>
Subject: Re: [PATCH] lpfc: Fix memory corruption of the lpfc_ncmd->list pointers
Date: Tue, 25 Apr 2017 10:58:44 -0700 [thread overview]
Message-ID: <20170425175844.GC3575@infradead.org> (raw)
In-Reply-To: <20170422004908.24261-1-jsmart2021@gmail.com>
On Fri, Apr 21, 2017 at 05:49:08PM -0700, jsmart2021@gmail.com wrote:
> This is a nvme-specific bug. The patch was cut against the
> linux-block tree, for-4.12/block tree. It should be pulled in through
> that tree.
It conflicts with your nvme changes that are in the nvme-4.12.
Can you respin it?
WARNING: multiple messages have this Message-ID (diff)
From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] lpfc: Fix memory corruption of the lpfc_ncmd->list pointers
Date: Tue, 25 Apr 2017 10:58:44 -0700 [thread overview]
Message-ID: <20170425175844.GC3575@infradead.org> (raw)
In-Reply-To: <20170422004908.24261-1-jsmart2021@gmail.com>
On Fri, Apr 21, 2017@05:49:08PM -0700, jsmart2021@gmail.com wrote:
> This is a nvme-specific bug. The patch was cut against the
> linux-block tree, for-4.12/block tree. It should be pulled in through
> that tree.
It conflicts with your nvme changes that are in the nvme-4.12.
Can you respin it?
next prev parent reply other threads:[~2017-04-25 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 0:49 [PATCH] lpfc: Fix memory corruption of the lpfc_ncmd->list pointers jsmart2021
2017-04-22 0:49 ` jsmart2021
2017-04-25 17:58 ` Christoph Hellwig [this message]
2017-04-25 17:58 ` Christoph Hellwig
2017-04-25 18:00 ` Christoph Hellwig
2017-04-25 18:00 ` Christoph Hellwig
2017-04-25 18:00 ` Christoph Hellwig
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=20170425175844.GC3575@infradead.org \
--to=hch@infradead.org \
--cc=dick.kennedy@broadcom.com \
--cc=emilne@redhat.com \
--cc=james.smart@broadcom.com \
--cc=jsmart2021@gmail.com \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--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.