From: Jan Beulich <jbeulich@suse.com>
To: Julien Grall <julien@xen.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"George Dunlap" <george.dunlap@citrix.com>,
"Ian Jackson" <iwj@xenproject.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] build: centralize / unify asm-offsets generation
Date: Thu, 1 Apr 2021 17:29:47 +0200 [thread overview]
Message-ID: <7977e181-a2d4-42ac-2294-34a49f6812c3@suse.com> (raw)
In-Reply-To: <089e3ff0-5633-02b4-baac-328ea8618469@xen.org>
On 01.04.2021 17:05, Julien Grall wrote:
> On 01/04/2021 09:33, Jan Beulich wrote:
>> --- a/xen/arch/arm/Makefile
>> +++ b/xen/arch/arm/Makefile
>> @@ -131,8 +131,8 @@ $(TARGET)-syms: prelink.o xen.lds
>> >$(@D)/$(@F).map
>> rm -f $(@D)/.$(@F).[0-9]*
>>
>> -asm-offsets.s: $(TARGET_SUBARCH)/asm-offsets.c
>> - $(CC) $(filter-out -flto,$(c_flags)) -S -o $@ $<
>> +.PHONY: include
>> +include:
>
> From a generic PoV, this target is meant to generate arch-specific
> include. Is that correct?
Yes, like is happening on x86 already.
Jan
next prev parent reply other threads:[~2021-04-01 15:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 8:33 [PATCH] build: centralize / unify asm-offsets generation Jan Beulich
2021-04-01 15:05 ` Julien Grall
2021-04-01 15:29 ` Jan Beulich [this message]
2021-04-15 9:50 ` Ping: " Jan Beulich
2021-04-20 15:29 ` Roger Pau Monné
2021-04-20 15:47 ` Jan Beulich
2021-04-20 16:20 ` Roger Pau Monné
2021-04-21 14:09 ` Jan Beulich
2021-04-27 9:05 ` Roger Pau Monné
2021-04-27 12:30 ` Jan Beulich
2021-04-27 13:31 ` Roger Pau Monné
2021-04-27 13:40 ` Jan Beulich
2021-04-27 14:13 ` Roger Pau Monné
2021-04-29 9:18 ` Ping: " Jan Beulich
2021-05-10 17:43 ` Julien Grall
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=7977e181-a2d4-42ac-2294-34a49f6812c3@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=julien@xen.org \
--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.