From: Klaus Jensen <its@irrelevant.dk>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Ankit Kumar <ankit.kumar@samsung.com>,
kbusch@kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/3] hw/nvme: bug fixes and doc update
Date: Tue, 8 Aug 2023 08:06:51 +0200 [thread overview]
Message-ID: <ZNHbe6zZZKhJO517@cormorant.local> (raw)
In-Reply-To: <165b8dea-9afb-3aeb-7551-9ecacb225fb0@tls.msk.ru>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
On Aug 8 09:04, Michael Tokarev wrote:
> 08.08.2023 00:27, Ankit Kumar wrote:
> > 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
>
> At least the CRC64 change smells like a -stable material, - the bug
> is present in, for example, qemu-7.2 too. But I don't know how important
> it is to keep nvme updated in 8.0 or before, and what the outcome of this
> bug is, to begin with. Somehow I think nvme was in preliminary shape
> before 8.0.
>
> Are the other changes also relevant for -stable?
>
> Please keep Cc: qemu-stable@nongnu.org for anything you think is worth
> to have in previous/stable releases.
>
Hi Michael,
Yes, this is stable worthy.
I'll add Cc: stable and fixes tags on relevant patches on the pull.
Thanks for the heads up!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-08-08 6:07 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 ` [PATCH 0/3] hw/nvme: bug fixes and doc update Ankit Kumar
[not found] ` <CGME20230807160837epcas5p3b360bae29265c0851f13491952b40f38@epcas5p3.samsung.com>
2023-08-07 21:27 ` [PATCH 1/3] hw/nvme: fix CRC64 for guard tag Ankit Kumar
2023-08-08 5:58 ` Klaus Jensen
[not found] ` <CGME20230807160838epcas5p389c82acd77fd8c74fc7f83300b9d0aa9@epcas5p3.samsung.com>
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
[not found] ` <CGME20230807160839epcas5p3fc18f1e23b454a6db48de18c822ac2d4@epcas5p3.samsung.com>
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 [this message]
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=ZNHbe6zZZKhJO517@cormorant.local \
--to=its@irrelevant.dk \
--cc=ankit.kumar@samsung.com \
--cc=kbusch@kernel.org \
--cc=mjt@tls.msk.ru \
--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 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).