From: Jiri Slaby <jirislaby@kernel.org>
To: Juergen Gross <jgross@suse.com>, Jan Beulich <jbeulich@suse.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] xen/hvc: replace BUG_ON() with negative return value
Date: Wed, 7 Jul 2021 12:58:14 +0200 [thread overview]
Message-ID: <b38eddf2-52af-3fa1-9cc0-681c094e327f@kernel.org> (raw)
In-Reply-To: <dd32b09b-7345-664b-165d-dfb30c285448@suse.com>
On 07. 07. 21, 12:40, Juergen Gross wrote:
>> And btw, since I've got puzzled by the linuxppc-dev@ in the recipients
>> list, I did look up relevant entries in ./MAINTAINERS. Shouldn't the
>> file be part of "XEN HYPERVISOR INTERFACE"?
>
> I wouldn't mind. Greg, Jiri, what do you think?
/me concurs.
thanks,
--
js
suse labs
prev parent reply other threads:[~2021-07-07 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 9:10 [PATCH v2] xen/hvc: replace BUG_ON() with negative return value Juergen Gross
2021-07-07 9:57 ` Jan Beulich
2021-07-07 10:40 ` Juergen Gross
2021-07-07 10:58 ` Jiri Slaby [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=b38eddf2-52af-3fa1-9cc0-681c094e327f@kernel.org \
--to=jirislaby@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).