From: Christopher Clark <christopher.w.clark@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Michal Orzel <michal.orzel@arm.com>,
meta-virtualization@lists.yoctoproject.org, nd <nd@arm.com>
Subject: Re: [PATCH 0/2] xen: PCI runqemu issue follow-up
Date: Fri, 17 Jun 2022 08:41:16 -0700 [thread overview]
Message-ID: <CACMJ4GZexTbtNFt27LfpHvgCSz0xorN+mE9HxsGEaqT-cDCBtg@mail.gmail.com> (raw)
In-Reply-To: <CADkTA4M_sMQd5v00NzmOas+j7HX0GopE6KRZZLV+TJmDr62fpg@mail.gmail.com>
On Tue, Jun 14, 2022 at 12:47 PM Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
>
> I was waiting to hear from Christopher on this one, so I'll let it
> soak a few more days before staging.
>
> Bruce
>
> On Thu, Jun 9, 2022 at 5:58 AM Michal Orzel <michal.orzel@arm.com> wrote:
> >
> > This series acts as a follow-up to the commit:
> > fb0a7b97db4f ("xen: Disable PCI on qemuarm with Xen")
> >
> > This wants to be backported to kirkstone.
Thanks for these patches and for working out what was needed for the
fix, Michal.
Apologies for the slow review - am catching up now after a few days
down with an injury (should be ok).
Christopher
> >
> > Michal Orzel (2):
> > Revert "xen: Disable PCI on qemuarm with Xen"
> > xen: Disable highmem on qemuarm
> >
> > classes/qemuboot-xen-defaults.bbclass | 6 ++++--
> > classes/qemuboot-xen-dtb.bbclass | 22 ----------------------
> > 2 files changed, 4 insertions(+), 24 deletions(-)
> >
> > --
> > 2.25.1
> >
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
next prev parent reply other threads:[~2022-06-17 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 9:57 [PATCH 0/2] xen: PCI runqemu issue follow-up Michal Orzel
2022-06-09 9:57 ` [PATCH 1/2] Revert "xen: Disable PCI on qemuarm with Xen" Michal Orzel
2022-06-09 10:01 ` [meta-virtualization] " Bertrand Marquis
2022-06-17 14:32 ` Christopher Clark
2022-06-09 9:57 ` [PATCH 2/2] xen: Disable highmem on qemuarm Michal Orzel
2022-06-09 10:01 ` [meta-virtualization] " Bertrand Marquis
2022-06-17 14:33 ` Christopher Clark
2022-06-14 19:47 ` [PATCH 0/2] xen: PCI runqemu issue follow-up Bruce Ashfield
2022-06-17 15:41 ` Christopher Clark [this message]
2022-06-20 7:33 ` [meta-virtualization] " Bertrand Marquis
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=CACMJ4GZexTbtNFt27LfpHvgCSz0xorN+mE9HxsGEaqT-cDCBtg@mail.gmail.com \
--to=christopher.w.clark@gmail.com \
--cc=bruce.ashfield@gmail.com \
--cc=meta-virtualization@lists.yoctoproject.org \
--cc=michal.orzel@arm.com \
--cc=nd@arm.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).