From: Klaus Jensen <its@irrelevant.dk>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Keith Busch <kbusch@kernel.org>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH-for-7.0 0/2] hw/nvme/ctrl: Buffer types cleanups
Date: Wed, 26 Jan 2022 10:05:15 +0100 [thread overview]
Message-ID: <YfEOy0x3w1acGcX+@apples> (raw)
In-Reply-To: <YY1cQEvB+YK1VA01@apples.localdomain>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
On Nov 11 19:09, Klaus Jensen wrote:
> On Nov 11 16:45, Philippe Mathieu-Daudé wrote:
> > Some trivial notes I took while reviewing CVE-2021-3947:
> > https://lore.kernel.org/qemu-devel/20211111153125.2258176-1-philmd@redhat.com/
> >
> > Based-on: <20211111153125.2258176-1-philmd@redhat.com>
> >
> > *** BLURB HERE ***
> >
> > Philippe Mathieu-Daudé (2):
> > hw/nvme/ctrl: Have nvme_addr_write() take const buffer
> > hw/nvme/ctrl: Pass buffers as 'void *' types
> >
> > hw/nvme/nvme.h | 4 ++--
> > hw/nvme/ctrl.c | 12 ++++++------
> > 2 files changed, 8 insertions(+), 8 deletions(-)
> >
>
> Thanks Philippe, LGTM.
>
> Reviewed-by: Klaus Jensen <k.jensen@samsung.com>
Applied to nvme-next. Thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-01-26 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 15:45 [PATCH-for-7.0 0/2] hw/nvme/ctrl: Buffer types cleanups Philippe Mathieu-Daudé
2021-11-11 15:45 ` [PATCH-for-7.0 1/2] hw/nvme/ctrl: Have nvme_addr_write() take const buffer Philippe Mathieu-Daudé
2021-11-11 15:45 ` [PATCH-for-7.0 2/2] hw/nvme/ctrl: Pass buffers as 'void *' types Philippe Mathieu-Daudé
2021-11-11 18:09 ` [PATCH-for-7.0 0/2] hw/nvme/ctrl: Buffer types cleanups Klaus Jensen
2022-01-26 9:05 ` 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=YfEOy0x3w1acGcX+@apples \
--to=its@irrelevant.dk \
--cc=kbusch@kernel.org \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.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 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).