From: James Smart <jsmart2021@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [bug report] scsi: lpfc: NVME Initiator: Merge into FC discovery
Date: Sat, 4 Mar 2017 09:48:44 -0800 [thread overview]
Message-ID: <bbb50009-e4c4-9185-9999-19ca46c28fd1@gmail.com> (raw)
In-Reply-To: <20170227163429.GA30640@mwanda>
On 2/27/2017 8:34 AM, Dan Carpenter wrote:
> Hello James Smart,
>
> This is a semi-automatic email about new static checker warnings.
>
> The patch a0f2d3ef374f: "scsi: lpfc: NVME Initiator: Merge into FC
> discovery" from Feb 12, 2017, leads to the following Smatch complaint:
>
>
Thanks. Issues addressed in the lpfc patch set just posted.
see http://marc.info/?l=linux-scsi&m=148864868315119&w=2
-- james
next prev parent reply other threads:[~2017-03-04 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 16:34 [bug report] scsi: lpfc: NVME Initiator: Merge into FC discovery Dan Carpenter
2017-03-04 17:48 ` James Smart [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-03 21:21 Dan Carpenter
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=bbb50009-e4c4-9185-9999-19ca46c28fd1@gmail.com \
--to=jsmart2021@gmail.com \
--cc=dan.carpenter@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox