My two cents worth is that it's (always) better to put ALL the commands into one place so that the entire set can be viewed at once and thus avoid inadvertent overloading of an opcode. Otherwise you don't know what you don't know. -----Original Message----- From: Linux-nvme [mailto:linux-nvme-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Keith Busch Sent: Thursday, April 16, 2015 8:52 AM To: Javier González Cc: hch@xxxxxxxxxxxxx; Matias Bjørling; axboe@xxxxxx; linux-kernel@xxxxxxxxxxxxxxx; linux-nvme@xxxxxxxxxxxxxxxxxxx; Keith Busch; linux-fsdevel@xxxxxxxxxxxxxxx Subject: Re: [PATCH 5/5 v2] nvme: LightNVM support On Thu, 16 Apr 2015, Javier González wrote: >> On 16 Apr 2015, at 16:55, Keith Busch <keith.busch@xxxxxxxxx> wrote: >> >> Otherwise it looks pretty good to me, but I think it would be cleaner >> if the lightnvm stuff is not mixed in the same file with the standard >> nvme command set. We might end up splitting nvme-core in the future >> anyway for command sets and transports. > > Would you be ok with having nvme-lightnvm for LightNVM specific > commands? Sounds good to me, but I don't really have a dog in this fight. :) -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
