From: Christoph Hellwig <hch@infradead.org>
To: James Smart <jsmart2021@gmail.com>
Cc: hare@suse.com, martin.petersen@oracle.com,
dick.kennedy@broadcom.com, linux-next@vger.kernel.org,
sfr@canb.auug.org.au, linux-nvme@lists.infradead.org,
sagi@grimberg.me, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] lpfc: add missing Kconfig NVME dependencies
Date: Thu, 23 Feb 2017 02:09:38 -0800 [thread overview]
Message-ID: <20170223100938.GA20495@infradead.org> (raw)
In-Reply-To: <58adba5f.BoP49Cv2S5zD9ZuD%jsmart2021@gmail.com>
On Wed, Feb 22, 2017 at 08:20:47AM -0800, James Smart wrote:
>
> add missing Kconfig NVME dependencies
>
> Can't believe I missed posting this
Oh. I'm not sure everyone is happy having to drag in the whole
nvme and nvme target stack when building lpfc. Is there a way
to make nvme optional? And in the future scsi as well?
next prev parent reply other threads:[~2017-02-23 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 16:20 [PATCH] lpfc: add missing Kconfig NVME dependencies James Smart
2017-02-22 19:35 ` Sagi Grimberg
2017-02-23 10:09 ` Christoph Hellwig [this message]
2017-02-23 15:51 ` James Smart
2018-02-15 19:00 ` Ewan D. Milne
2018-02-15 19:02 ` Ewan D. Milne
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=20170223100938.GA20495@infradead.org \
--to=hch@infradead.org \
--cc=dick.kennedy@broadcom.com \
--cc=hare@suse.com \
--cc=jsmart2021@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sagi@grimberg.me \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox