diff options
| author | James Smart <[email protected]> | 2017-03-08 22:36:01 +0000 |
|---|---|---|
| committer | Martin K. Petersen <[email protected]> | 2017-03-15 17:37:18 +0000 |
| commit | 7d7080335f8d93a51e8238b6e85be8af4ba452b6 (patch) | |
| tree | c93ca817a5d6b00f7a3920f75c59f3f83c2dc0dd /net/unix/garbage.c | |
| parent | scsi: ufs: don't check unsigned type for a negative value (diff) | |
| download | kernel-7d7080335f8d93a51e8238b6e85be8af4ba452b6.tar.gz kernel-7d7080335f8d93a51e8238b6e85be8af4ba452b6.zip | |
scsi: lpfc: Finalize Kconfig options for nvme
Reviewing the result of what was just added for Kconfig, we made a poor
choice. It worked well for full kernel builds, but not so much for how
it would be deployed on a distro.
Here's the final result:
- lpfc will compile in NVME initiator and/or NVME target support based
on whether the kernel has the corresponding subsystem support.
Kconfig is not used to drive this specifically for lpfc.
- There is a module parameter, lpfc_enable_fc4_type, that indicates
whether the ports will do FCP-only or FCP & NVME (NVME-only not yet
possible due to dependency on fc transport). As FCP & NVME divvys up
exchange resources, and given NVME will not be often initially, the
default is changed to FCP only.
Signed-off-by: Dick Kennedy <[email protected]>
Signed-off-by: James Smart <[email protected]>
Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'net/unix/garbage.c')
0 files changed, 0 insertions, 0 deletions