From: Markus Armbruster <armbru@redhat.com>
To: "Wang, Wenchao" <wenchao.wang@intel.com>
Cc: qemu-trivial@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Yuan, Hang" <hang.yuan@intel.com>
Subject: Re: [PATCH 1/1] MAINTAINERS: Update maintainers for Guest x86 HAXM CPUs
Date: Mon, 21 Mar 2022 16:14:24 +0100 [thread overview]
Message-ID: <875yo7pcbz.fsf@pond.sub.org> (raw)
In-Reply-To: <DM6PR11MB40905967203E4917E78C773487119@DM6PR11MB4090.namprd11.prod.outlook.com> (Wenchao Wang's message of "Wed, 16 Mar 2022 00:47:52 +0000")
Perhaps this can go via qemu-trivial (cc'ed).
"Wang, Wenchao" <wenchao.wang@intel.com> writes:
> diff --git a/MAINTAINERS b/MAINTAINERS
> index f2e9ce1da2..36f877cf74 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -492,7 +492,6 @@ Guest CPU Cores (HAXM)
> ---------------------
> X86 HAXM CPUs
> M: Wenchao Wang <wenchao.wang@intel.com>
> -M: Colin Xu <colin.xu@intel.com>
> L: haxm-team@intel.com
> W: https://github.com/intel/haxm/issues
> S: Maintained
> --
> 2.17.1
Patch git-am fails with "error: corrupt patch at line 7".
For a trivial patch like this one, the maintainer may be willing to work
around. To post real work, you'll have to fix your mail sending, I'm
afraid.
Patch makes sense; mail to colin.xu@intel.com bounces.
Reviewed-by: Markus Armbruster <armbru@redhat.com>
next prev parent reply other threads:[~2022-03-21 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 0:47 [PATCH 1/1] MAINTAINERS: Update maintainers for Guest x86 HAXM CPUs Wang, Wenchao
2022-03-21 15:14 ` Markus Armbruster [this message]
2022-03-23 18:05 ` Philippe Mathieu-Daudé
2022-03-24 0:55 ` Wang, Wenchao
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=875yo7pcbz.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=hang.yuan@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=wenchao.wang@intel.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).