From: Bertrand Marquis <Bertrand.Marquis@arm.com>
To: Rahul Singh <Rahul.Singh@arm.com>
Cc: Xen developer discussion <xen-devel@lists.xenproject.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Henry Wang <Henry.Wang@arm.com>
Subject: Re: [PATCH 0/2] xen/arm: static event channel
Date: Mon, 26 Sep 2022 12:12:28 +0000 [thread overview]
Message-ID: <D0DBE432-5636-47AD-B6B6-CCC1D636CD19@arm.com> (raw)
In-Reply-To: <cover.1663928523.git.rahul.singh@arm.com>
Hi Rahul,
Please give the necessary justification for inclusion in 4.17:
- severity of the bug fixed
- probability and impact of potential issues that the patch could add.
thanks
Bertrand
> On 23 Sep 2022, at 13:02, Rahul Singh <Rahul.Singh@arm.com> wrote:
>
> This patch series fix issues related to static event channel series.
>
> Rahul Singh (2):
> xen: Add static event channel in SUPPORT.md on ARM
> xen/arm: fix booting ACPI based system after static evtchn series
>
> SUPPORT.md | 7 +++++++
> xen/arch/arm/setup.c | 5 +++--
> 2 files changed, 10 insertions(+), 2 deletions(-)
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-09-26 12:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 11:02 [PATCH 0/2] xen/arm: static event channel Rahul Singh
2022-09-23 11:02 ` [PATCH 1/2] xen: Add static event channel in SUPPORT.md on ARM Rahul Singh
2022-09-26 8:41 ` Ayan Kumar Halder
2022-09-30 10:37 ` Bertrand Marquis
2022-09-23 11:02 ` [PATCH 2/2] xen/arm: fix booting ACPI based system after static evtchn series Rahul Singh
2022-09-23 12:10 ` Ayan Kumar Halder
2022-09-23 15:42 ` Rahul Singh
2022-09-26 7:38 ` Jan Beulich
2022-09-26 8:40 ` Ayan Kumar Halder
2022-09-30 10:37 ` Bertrand Marquis
2022-09-26 12:12 ` Bertrand Marquis [this message]
2022-09-27 8:41 ` [PATCH 0/2] xen/arm: static event channel Rahul Singh
2022-09-27 8:52 ` Henry Wang
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=D0DBE432-5636-47AD-B6B6-CCC1D636CD19@arm.com \
--to=bertrand.marquis@arm.com \
--cc=Henry.Wang@arm.com \
--cc=Rahul.Singh@arm.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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).