From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: James Smart <jsmart2021@gmail.com>
Cc: linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org,
sfr@canb.auug.org.au, martin.petersen@oracle.com,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
hare@suse.com, Dick Kennedy <dick.kennedy@broadcom.com>,
James Smart <james.smart@broadcom.com>
Subject: Re: [PATCH] lpfc: fix build issue if NVME_FC_TARGET is not defined
Date: Wed, 17 May 2017 20:23:31 -0400 [thread overview]
Message-ID: <yq1tw4j6mik.fsf@oracle.com> (raw)
In-Reply-To: <20170517035229.1145-1-jsmart2021@gmail.com> (James Smart's message of "Tue, 16 May 2017 20:52:29 -0700")
James,
> fix build issue if NVME_FC_TARGET is not defined. noop the code.
> The code will never be invoked if target mode is not enabled.
Applied to 4.12/scsi-fixes. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: martin.petersen@oracle.com (Martin K. Petersen)
Subject: [PATCH] lpfc: fix build issue if NVME_FC_TARGET is not defined
Date: Wed, 17 May 2017 20:23:31 -0400 [thread overview]
Message-ID: <yq1tw4j6mik.fsf@oracle.com> (raw)
In-Reply-To: <20170517035229.1145-1-jsmart2021@gmail.com> (James Smart's message of "Tue, 16 May 2017 20:52:29 -0700")
James,
> fix build issue if NVME_FC_TARGET is not defined. noop the code.
> The code will never be invoked if target mode is not enabled.
Applied to 4.12/scsi-fixes. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-05-18 0:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 3:52 [PATCH] lpfc: fix build issue if NVME_FC_TARGET is not defined James Smart
2017-05-17 3:52 ` James Smart
2017-05-18 0:23 ` Martin K. Petersen [this message]
2017-05-18 0:23 ` 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=yq1tw4j6mik.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=dick.kennedy@broadcom.com \
--cc=hare@suse.com \
--cc=james.smart@broadcom.com \
--cc=jsmart2021@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.