From: Charles Machalow <csm10495@gmail.com> To: linux-nvme@lists.infradead.org Cc: csm10495@gmail.com, marta.rybczynska@kalray.eu, Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>, linux-kernel@vger.kernel.org Subject: [PATCH] nvme: change nvme_passthru_cmd64 to explicitly mark rsvd Date: Mon, 4 Nov 2019 22:15:10 -0800 [thread overview] Message-ID: <20191105061510.22233-1-csm10495@gmail.com> (raw) Changing nvme_passthru_cmd64 to add a field: rsvd2. This field is an explicit marker for the padding space added on certain platforms as a result of the enlargement of the result field from 32 bit to 64 bits in size. --- include/uapi/linux/nvme_ioctl.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/uapi/linux/nvme_ioctl.h b/include/uapi/linux/nvme_ioctl.h index e168dc59e..d99b5a772 100644 --- a/include/uapi/linux/nvme_ioctl.h +++ b/include/uapi/linux/nvme_ioctl.h @@ -63,6 +63,7 @@ struct nvme_passthru_cmd64 { __u32 cdw14; __u32 cdw15; __u32 timeout_ms; + __u32 rsvd2; __u64 result; }; -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Charles Machalow <csm10495@gmail.com> To: linux-nvme@lists.infradead.org Cc: Sagi Grimberg <sagi@grimberg.me>, csm10495@gmail.com, linux-kernel@vger.kernel.org, Jens Axboe <axboe@fb.com>, marta.rybczynska@kalray.eu, Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de> Subject: [PATCH] nvme: change nvme_passthru_cmd64 to explicitly mark rsvd Date: Mon, 4 Nov 2019 22:15:10 -0800 [thread overview] Message-ID: <20191105061510.22233-1-csm10495@gmail.com> (raw) Changing nvme_passthru_cmd64 to add a field: rsvd2. This field is an explicit marker for the padding space added on certain platforms as a result of the enlargement of the result field from 32 bit to 64 bits in size. --- include/uapi/linux/nvme_ioctl.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/uapi/linux/nvme_ioctl.h b/include/uapi/linux/nvme_ioctl.h index e168dc59e..d99b5a772 100644 --- a/include/uapi/linux/nvme_ioctl.h +++ b/include/uapi/linux/nvme_ioctl.h @@ -63,6 +63,7 @@ struct nvme_passthru_cmd64 { __u32 cdw14; __u32 cdw15; __u32 timeout_ms; + __u32 rsvd2; __u64 result; }; -- 2.17.1 _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2019-11-05 6:15 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-05 6:15 Charles Machalow [this message] 2019-11-05 6:15 ` [PATCH] nvme: change nvme_passthru_cmd64 to explicitly mark rsvd Charles Machalow 2019-11-05 7:39 ` Marta Rybczynska 2019-11-05 7:39 ` Marta Rybczynska 2019-11-05 15:31 ` Christoph Hellwig 2019-11-05 15:31 ` Christoph Hellwig 2019-11-06 0:08 ` Sasha Levin 2019-11-06 0:08 ` Sasha Levin 2019-11-06 0:18 ` Keith Busch 2019-11-06 0:18 ` Keith Busch 2019-11-06 1:09 ` Christoph Hellwig 2019-11-06 1:09 ` Christoph Hellwig 2019-11-05 14:34 ` Christoph Hellwig 2019-11-05 14:34 ` Christoph Hellwig 2019-11-05 15:26 ` Keith Busch 2019-11-05 15:26 ` Keith Busch 2019-11-05 20:56 ` Charles Machalow 2019-11-05 20:56 ` Charles Machalow 2019-11-05 21:21 ` Keith Busch 2019-11-05 21:21 ` Keith Busch
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=20191105061510.22233-1-csm10495@gmail.com \ --to=csm10495@gmail.com \ --cc=axboe@fb.com \ --cc=hch@lst.de \ --cc=kbusch@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nvme@lists.infradead.org \ --cc=marta.rybczynska@kalray.eu \ --cc=sagi@grimberg.me \ /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: linkBe 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.