From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Dmytro Prokopchuk1 <dmytro_prokopchuk1@epam.com>
Cc: xen-devel@lists.xenproject.org,
Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH] automation/eclair: export XEN_TARGET_ARCH during assignment
Date: Tue, 19 May 2026 13:09:31 +0200 [thread overview]
Message-ID: <40a468313da350be8b60df32a7c58083@bugseng.com> (raw)
In-Reply-To: <50f31733-3048-4512-af12-50dd9ba3cf8c@epam.com>
On 2026-05-19 13:03, Dmytro Prokopchuk1 wrote:
> Hello Nicola,
>
> On 5/19/26 13:45, Nicola Vetrini wrote:
>> On 2026-05-19 12:27, Dmytro Prokopchuk1 wrote:
>>> Move XEN_TARGET_ARCH export into the architecture selection
>>> branches instead of exporting the variable before assignment.
>>> This ensures the selected architecture value is correctly
>>> propagated.
>>>
>>
>> Did you see a case where this is not correctly propagated? As far as I
> I didn't see a case.
>> understand, the value of XEN_TARGET_ARCH seen by subprocesses is the
>> last value set for the variable, regardless of where the export
>> command
>> is placed.
> Yes, you are right. It works in that way.
> IMO, exporting empty variable looks strange...
>
> Anyway up to you to judge if this patch is needed or not.
>
Indeed it is a bit strange. To avoid this we should perhaps move the
export after the if, so that it is obvious that it contains the correct
value
> BR, Dmytro.
>>> No functional changes.
>>>
>>> Signed-off-by: Dmytro Prokopchuk <dmytro_prokopchuk1@epam.com>
>>> ---
>>> automation/eclair_analysis/prepare.sh | 6 ++----
>>> 1 file changed, 2 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/automation/eclair_analysis/prepare.sh b/automation/
>>> eclair_analysis/prepare.sh
>>> index e941e6edc4..fde83c2d2d 100755
>>> --- a/automation/eclair_analysis/prepare.sh
>>> +++ b/automation/eclair_analysis/prepare.sh
>>> @@ -22,12 +22,10 @@ if [ $# -ne 1 ]; then
>>> exit 1
>>> fi
>>>
>>> -export XEN_TARGET_ARCH
>>> -
>>> if [ "$1" = "X86_64" ]; then
>>> - XEN_TARGET_ARCH=x86_64
>>> + export XEN_TARGET_ARCH=x86_64
>>> elif [ "$1" = "ARM64" ]; then
>>> - XEN_TARGET_ARCH=arm64
>>> + export XEN_TARGET_ARCH=arm64
>>> else
>>> fatal "Unknown configuration: $1"
>>> fi
>>
--
Nicola Vetrini, B.Sc.
Software Engineer
BUGSENG (https://bugseng.com)
LinkedIn: https://www.linkedin.com/in/nicola-vetrini-a42471253
prev parent reply other threads:[~2026-05-19 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 10:27 [PATCH] automation/eclair: export XEN_TARGET_ARCH during assignment Dmytro Prokopchuk1
2026-05-19 10:32 ` Jan Beulich
2026-05-19 10:45 ` Nicola Vetrini
2026-05-19 11:03 ` Dmytro Prokopchuk1
2026-05-19 11:09 ` Nicola Vetrini [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=40a468313da350be8b60df32a7c58083@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=cardoe@cardoe.com \
--cc=dmytro_prokopchuk1@epam.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.