From: Ankit Kumar <ankit.kumar@samsung.com>
To: kbusch@kernel.org, its@irrelevant.dk
Cc: qemu-devel@nongnu.org, Ankit Kumar <ankit.kumar@samsung.com>
Subject: [PATCH 0/3] hw/nvme: bug fixes and doc update
Date: Tue, 8 Aug 2023 02:57:42 +0530 [thread overview]
Message-ID: <20230807212745.70151-1-ankit.kumar@samsung.com> (raw)
In-Reply-To: CGME20230807160836epcas5p34398954fecd7388469012404b09b78f9@epcas5p3.samsung.com
This series fixes two bugs
1. CRC64 generation when metadata buffer is used.
2. Protection information disable check for Type 3 protection.
This series also updates the documentaion for pi (protection information),
and adds missing pif (protection information format) entry.
Ankit Kumar (3):
hw/nvme: fix CRC64 for guard tag
hw/nvme: fix disable pi checks for Type 3 protection
docs: update hw/nvme documentation for protection information
docs/system/devices/nvme.rst | 10 +++++++---
hw/nvme/dif.c | 9 +++++----
2 files changed, 12 insertions(+), 7 deletions(-)
--
2.25.1
next parent reply other threads:[~2023-08-08 1:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230807160836epcas5p34398954fecd7388469012404b09b78f9@epcas5p3.samsung.com>
2023-08-07 21:27 ` Ankit Kumar [this message]
2023-08-07 21:27 ` [PATCH 1/3] hw/nvme: fix CRC64 for guard tag Ankit Kumar
2023-08-08 5:58 ` Klaus Jensen
2023-08-07 21:27 ` [PATCH 2/3] hw/nvme: fix disable pi checks for Type 3 protection Ankit Kumar
2023-08-08 5:57 ` Klaus Jensen
2023-08-07 21:27 ` [PATCH 3/3] docs: update hw/nvme documentation for protection information Ankit Kumar
2023-08-08 5:59 ` Klaus Jensen
2023-08-08 6:04 ` [PATCH 0/3] hw/nvme: bug fixes and doc update Michael Tokarev
2023-08-08 6:06 ` Klaus Jensen
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=20230807212745.70151-1-ankit.kumar@samsung.com \
--to=ankit.kumar@samsung.com \
--cc=its@irrelevant.dk \
--cc=kbusch@kernel.org \
--cc=qemu-devel@nongnu.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 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.