From: Tokunori Ikegami <ikegami.t@gmail.com>
To: linux-nvme@lists.infradead.org
Cc: Tokunori Ikegami <ikegami.t@gmail.com>
Subject: [PATCH 0/2] nvme/ioctl: improve user request allocation
Date: Sat, 7 Jun 2025 05:16:08 +0900 [thread overview]
Message-ID: <20250606201654.9558-1-ikegami.t@gmail.com> (raw)
Previously nvme command copied for the user request allocation.
But the nvme command already allocated for the request.
So change to just set the nvme command values directly without the copy.
Also fixed the checkpatch.pl warnings for the unsigned values.
Tokunori Ikegami (2):
nvme/ioctl: split user request allocation from user command submission
nvme/ioctl: fix unsigned value as unsigned int value
drivers/nvme/host/core.c | 10 +-
drivers/nvme/host/ioctl.c | 230 +++++++++++++++++++++-----------------
2 files changed, 134 insertions(+), 106 deletions(-)
--
2.48.1
next reply other threads:[~2025-06-06 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 20:16 Tokunori Ikegami [this message]
2025-06-06 20:16 ` [PATCH 1/2] nvme/ioctl: split user request allocation from user command submission Tokunori Ikegami
2025-06-06 20:16 ` [PATCH 2/2] nvme/ioctl: fix unsigned value as unsigned int value Tokunori Ikegami
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=20250606201654.9558-1-ikegami.t@gmail.com \
--to=ikegami.t@gmail.com \
--cc=linux-nvme@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).