From: "Anthony PERARD" <anthony.perard@vates.tech>
To: "Stefano Stabellini" <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
michal.orzel@amd.com, jbeulich@suse.com, julien@xen.org,
roger.pau@citrix.com, bertrand.marquis@arm.com,
federico.serafini@bugseng.com,
"Nicola Vetrini" <nicola.vetrini@bugseng.com>
Subject: Re: [PATCH v6] automation/eclair: update configuration of D4.10
Date: Mon, 07 Jul 2025 15:19:39 +0000 [thread overview]
Message-ID: <aGvliTiOQCBl1t0v@l14> (raw)
In-Reply-To: <aGvCAbCGfQ8Vzcp2@l14>
On Mon, Jul 07, 2025 at 12:48:06PM +0000, Anthony PERARD wrote:
> On Mon, Jun 23, 2025 at 06:19:27PM -0700, Stefano Stabellini wrote:
> > diff --git a/xen/include/xen/compile.h.in b/xen/include/xen/compile.h.in
> > index 3151d1e7d1..9206341ba6 100644
> > --- a/xen/include/xen/compile.h.in
> > +++ b/xen/include/xen/compile.h.in
> > @@ -1,3 +1,6 @@
> > +#ifndef XEN_COMPILE_H
> > +#define XEN_COMPILE_H
> > +
> > #define XEN_COMPILE_DATE "@@date@@"
> > #define XEN_COMPILE_TIME "@@time@@"
> > #define XEN_COMPILE_BY "@@whoami@@"
> > diff --git a/xen/tools/process-banner.sed b/xen/tools/process-banner.sed
> > index 56c76558bc..4cf3f9a116 100755
> > --- a/xen/tools/process-banner.sed
> > +++ b/xen/tools/process-banner.sed
> > @@ -12,3 +12,8 @@ s_(.*)_"\1\\n"_
> >
> > # Trailing \ on all but the final line.
> > $!s_$_ \\_
> > +
> > +# Append closing header guard
> > +$a\
> > +\
> > +#endif /* XEN_COMPILE_H */
>
> Is it wise to put the closing header guard in a file call
> "process-banner" ? It's not call compile.h-footer.sed.
>
> There's a few way to make this better:
> - simple add the header guard from the Makefile, both opening and
> closing.
> - Do some more sed with something like:
> sed -rf process-banner.sed < .banner >> .banner.processed.tmp
> sed -e 's/@@date@@/$(XEN_BUILD_DATE)/g' \
> ... \
> -e '/XEN_BANNER/r .banner.processed.tmp'
> # and having the closing header guard in "compile.h.in"
> This will add the outpot of process-banner.sed in the lines after
> "#define XEN_BANNER", and so before the closing header guard.
> - rename the sed command file
> (- a forth option would be to use filechk make macro, but the check for
> if [ ! -r $@ -o -O $@ ] would be annoying to reproduce.)
>
> Another thing, this could be done in a patch that isn't called
> "automation/eclair: update configuration of D4.10".
Sorry, I failed to notice the patch was already commited. I guess it's
good enough like that.
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
prev parent reply other threads:[~2025-07-07 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 1:19 [PATCH v6] automation/eclair: update configuration of D4.10 Stefano Stabellini
2025-06-24 6:13 ` Jan Beulich
2025-07-02 14:05 ` Dmytro Prokopchuk1
2025-07-07 12:48 ` Anthony PERARD
2025-07-07 15:19 ` Anthony PERARD [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=aGvliTiOQCBl1t0v@l14 \
--to=anthony.perard@vates.tech \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=federico.serafini@bugseng.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=nicola.vetrini@bugseng.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.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.