[Nexus 5 Original Android Development] dechronic:
Sorry for taking so long to reply. I looked at it yesterday and got sidetracked.

The fstab files only have f2fs entries for the /data partition.

For f2fs-all usually the /system, /data & /cache partitions are all formatted as f2fs and that is reflected in the ramdisk.

Here are my suggested entries for you. Just one question...is there a reason you have to different entries to mount the (internal?) SDcard between the two files? If that's their defaults I wouldn't touch them.

fstab.qcom

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

/dev/partitions/system /system f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait
/dev/partitions/cache /cache f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait,check
/dev/partitions/userdata /data f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,flush_merge,errors=recover wait,nonremovable,encryptable=footer,length=-16384

/devices/platform/msm_sdcc.4/mmc_host/mmc2* auto auto defaults voldmanaged=sdcard0:auto,noemulatedsd
/devices/platform/msm_sdcc.2/mmc_host/mmc0* auto vfat defaults voldmanaged=sdcard1:14,nonremovable,noemulatedsd
/devices/platform/msm_hsusb_host.0* auto auto defaults voldmanaged=usbdisk0:auto

/dev/block/platform/msm_sdcc.2/by-num/p1 /cust vfat ro defaults
/dev/block/platform/msm_sdcc.2/by-num/p1 /boot vfat defaults recoveryonly
/dev/null /recovery emmc defaults recoveryonly

# zRAM
/dev/block/zram0 none swap defaults zramsize=201326592

fstab.qcom.lvm

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

/dev/partitions/system /system f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait
/dev/partitions/cache /cache f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait,check
/dev/partitions/userdata /data f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,flush_merge,errors=recover wait,nonremovable,encryptable=footer,length=-16384

/devices/platform/msm_sdcc.4/mmc_host/mmc2* auto auto defaults voldmanaged=sdcard0:auto,noemulatedsd
/devices/virtual/block/dm-3* auto vfat defaults voldmanaged=sdcard1:nonremovable,noemulatedsd
/devices/platform/msm_hsusb_host.0* auto auto defaults voldmanaged=usbdisk0:auto

/dev/block/platform/msm_sdcc.2/by-num/p1 /cust vfat ro defaults
/dev/block/platform/msm_sdcc.2/by-num/p1 /boot vfat defaults recoveryonly
/dev/null /recovery emmc defaults recoveryonly

# zRAM
/dev/block/zram0 none swap defaults zramsize=201326592

---------- Post added at 07:15 AM ---------- Previous post was at 07:08 AM ----------

Which kernel are you asking about? CM12, based on lollipop, is still AOSP last I heard. So any AOSP based kernel will work with it, including ElementalX, CodeBlue, Franco, etc. myfluxi has his own version of CM which is almost entirely CAF for which only his kernel and one that neobuddy89 was developing for it. neobuddy89's development of his kernel for it was/is on pause until myfluxi was satisfied that it is stable enough or something along those lines, I may be wrong, basing it on my memory of posts I read a couple of weeks ago.