From: Jan Beulich <jbeulich@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
JulienGrall <julien@xen.org>, Wei Liu <wl@xen.org>,
Konrad Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
AndrewCooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH v2 0/2] x86: clang build check adjustments
Date: Fri, 15 Nov 2019 16:00:42 +0100 [thread overview]
Message-ID: <5ee086c8-3527-99e6-aad6-238f031dd41f@suse.com> (raw)
In-Reply-To: <20191115143959.GI72134@Air-de-Roger>
On 15.11.2019 15:45, Roger Pau Monné wrote:
> On Fri, Nov 15, 2019 at 11:43:21AM +0100, Jan Beulich wrote:
>> 1: fix clang .macro retention check
>> 2: clang: move and fix .skip check
>
> For both:
>
> Tested-by: Roger Pau Monné <roger.pasu@citrix.com>
> [On FreeBSD and Debian 9.5]
Thanks much. I'll take the liberty and drop the seemingly stray
's' from your email address here.
> Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
>
> Note there's a typo in this email's subject (clank v clang).
Yeah, I had noticed this right after sending. Fingers and brain
must have had a disconnect.
> Also, if
> possible, could both patches have the same prefix? (x86/clang)
I did notice the prefix difference before sending the series.
I wouldn't mind making both just x86: (moving "clang" elsewhere
in the title of yours), but I don't want to make mine have
x86/clang, because I think these should represent subsystems or
alike.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-11-15 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 10:43 [Xen-devel] [PATCH v2 0/2] x86: clank build check adjustments Jan Beulich
2019-11-15 10:48 ` [Xen-devel] [PATCH v2 1/2] x86: fix clang .macro retention check Jan Beulich
2019-11-15 10:48 ` [Xen-devel] [PATCH v2 2/2] x86/clang: move and fix .skip check Jan Beulich
2019-11-15 14:45 ` [Xen-devel] [PATCH v2 0/2] x86: clank build check adjustments Roger Pau Monné
2019-11-15 14:50 ` Andrew Cooper
2019-11-15 15:00 ` Jan Beulich [this message]
2019-11-15 15:20 ` [Xen-devel] [PATCH v2 0/2] x86: clang " Roger Pau Monné
2019-11-30 16:08 ` [Xen-devel] [PATCH v2 0/2] x86: clank " Doug Goldstein
2019-12-01 13:31 ` Roger Pau Monné
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=5ee086c8-3527-99e6-aad6-238f031dd41f@suse.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=julien@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=roger.pau@citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.