From: Igor Mammedov <imammedo@redhat.com>
To: Jonathan Cameron via <qemu-devel@nongnu.org>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
<linuxarm@huawei.com>, "Michael S . Tsirkin" <mst@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
"Ben Widawsky" <bwidawsk@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 0/3] hw/cxl, hw/machine, hw/i386: Misc minor fixes / cleanup
Date: Mon, 11 Jul 2022 14:42:10 +0200 [thread overview]
Message-ID: <20220711144210.567505a9@redhat.com> (raw)
In-Reply-To: <20220701132300.2264-1-Jonathan.Cameron@huawei.com>
On Fri, 1 Jul 2022 14:22:57 +0100
Jonathan Cameron via <qemu-devel@nongnu.org> wrote:
> Three more or less less unrelated fixes for recently added CXL code.
>
> Jonathan Cameron (3):
> hw/machine: Clear out left over CXL related pointer from move of state
> handling to machines.
> hw/i386/pc: Always place CXL Memory Regions after device_memory
> hw/cxl: Fix size of constant in interleave granularity function.
>
> hw/i386/pc.c | 6 ++----
> include/hw/boards.h | 1 -
> include/hw/cxl/cxl_component.h | 2 +-
> 3 files changed, 3 insertions(+), 6 deletions(-)
>
For whole series:
Acked-by: Igor Mammedov <imammedo@redhat.com>
next prev parent reply other threads:[~2022-07-11 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 13:22 [PATCH 0/3] hw/cxl, hw/machine, hw/i386: Misc minor fixes / cleanup Jonathan Cameron via
2022-07-01 13:22 ` [PATCH 1/3] hw/machine: Clear out left over CXL related pointer from move of state handling to machines Jonathan Cameron via
2022-07-01 13:22 ` [PATCH 2/3] hw/i386/pc: Always place CXL Memory Regions after device_memory Jonathan Cameron via
2022-07-01 13:23 ` [PATCH 3/3] hw/cxl: Fix size of constant in interleave granularity function Jonathan Cameron via
2022-07-11 12:42 ` Igor Mammedov [this message]
2022-07-19 14:09 ` [PATCH 0/3] hw/cxl, hw/machine, hw/i386: Misc minor fixes / cleanup Peter Maydell
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=20220711144210.567505a9@redhat.com \
--to=imammedo@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=bwidawsk@kernel.org \
--cc=linuxarm@huawei.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shameerali.kolothum.thodi@huawei.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 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).