From: Ian Jackson <iwj@xenproject.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel\@lists.xenproject.org"
<xen-devel@lists.xenproject.org>,
Elena Ufimtseva <elena.ufimtseva@oracle.com>,
Wei Liu <wl@xen.org>
Subject: Re: [PATCH] tools/gdbsx: drop stray recursion into tools/include/
Date: Thu, 15 Oct 2020 14:17:18 +0100 [thread overview]
Message-ID: <24456.19422.318790.279648@mariner.uk.xensource.com> (raw)
In-Reply-To: <ece6c5c2-43f8-36d2-370c-37d988baeb87@suse.com>
Jan Beulich writes ("[PATCH] tools/gdbsx: drop stray recursion into tools/include/"):
> Doing so isn't appropriate here - this gets done very early in the build
> process. If the directory is mean to to be buildable on its own,
> different arrangements would be needed.
>
> The issue has become more pronounced by 47654a0d7320 ("tools/include:
> fix (drop) dependencies of when to populate xen/"), but was there before
> afaict.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Ian Jackson <ian.jackson@eu.citrix.com>
next prev parent reply other threads:[~2020-10-15 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 8:42 [PATCH] tools/gdbsx: drop stray recursion into tools/include/ Jan Beulich
2020-10-15 13:17 ` Ian Jackson [this message]
2020-10-16 13:26 ` Wei Liu
2020-10-16 13:31 ` Wei Liu
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=24456.19422.318790.279648@mariner.uk.xensource.com \
--to=iwj@xenproject.org \
--cc=elena.ufimtseva@oracle.com \
--cc=jbeulich@suse.com \
--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).