From: Klaus Jensen <its@irrelevant.dk>
To: Gollu Appalanaidu <anaidu.gollu@samsung.com>
Cc: fam@euphon.net, kwolf@redhat.com, qemu-block@nongnu.org,
k.jensen@samsung.com, qemu-devel@nongnu.org, mreitz@redhat.com,
stefanha@redhat.com, kbusch@kernel.org
Subject: Re: [PATCH 2/2] hw/block/nvme: align reserved fields declarations
Date: Thu, 15 Apr 2021 08:55:03 +0200 [thread overview]
Message-ID: <YHfjR1KMzUsJXgWY@apples.localdomain> (raw)
In-Reply-To: <20210317093006.31404-2-anaidu.gollu@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
On Mar 17 15:00, Gollu Appalanaidu wrote:
>Align the Reserved fields declaration in NvmeBar
>
>Signed-off-by: Gollu Appalanaidu <anaidu.gollu@samsung.com>
>---
> include/block/nvme.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/include/block/nvme.h b/include/block/nvme.h
>index fc65cfcb01..e5bd00bb85 100644
>--- a/include/block/nvme.h
>+++ b/include/block/nvme.h
>@@ -7,7 +7,7 @@ typedef struct QEMU_PACKED NvmeBar {
> uint32_t intms;
> uint32_t intmc;
> uint32_t cc;
>- uint32_t rsvd1;
>+ uint8_t rsvd24[4];
> uint32_t csts;
> uint32_t nssrc;
> uint32_t aqa;
>--
>2.17.1
>
Thanks. Applied to nvme-next with a small commit message fixup!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-04-15 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210317093352epcas5p3193a70101b750934fabcb2540129e499@epcas5p3.samsung.com>
2021-03-17 9:30 ` [PATCH 1/2] hw/block/nvme: align with existing style Gollu Appalanaidu
[not found] ` <CGME20210317093452epcas5p1be6015c3cec5c7c8a82c779f511d8bd0@epcas5p1.samsung.com>
2021-03-17 9:30 ` [PATCH 2/2] hw/block/nvme: align reserved fields declarations Gollu Appalanaidu
2021-04-15 6:55 ` Klaus Jensen [this message]
2021-04-15 6:53 ` [PATCH 1/2] hw/block/nvme: align with existing style 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=YHfjR1KMzUsJXgWY@apples.localdomain \
--to=its@irrelevant.dk \
--cc=anaidu.gollu@samsung.com \
--cc=fam@euphon.net \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.