From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v8 1/4] Refactor regen.sh script to generate syscalls
Date: Thu, 31 Oct 2024 17:21:05 +0100 [thread overview]
Message-ID: <ZyOucZF2mzL-Jame@yuki.lan> (raw)
In-Reply-To: <20241031-generate_syscalls-v8-1-8e35a9d6783b@suse.com>
Hi!
> +while IFS= read -r arch; do
> + (
> + echo
> + case ${arch} in
> + sparc64) echo "#if defined(__sparc__) && defined(__arch64__)" ;;
> + sparc) echo "#if defined(__sparc__) && !defined(__arch64__)" ;;
> + s390) echo "#if defined(__s390__) && !defined(__s390x__)" ;;
> + mips64n32) echo "#if defined(__mips__) && defined(_ABIN32)" ;;
> + mips64) echo "#if defined(__mips__) && defined(_ABI64)" ;;
> + mipso32) echo "#if defined(__mips__) && defined(_ABIO32) && _MIPS_SZLONG == 32" ;;
It would be nice to get a confirmation from someone who knows mips that
these changes in ifdefs are okay, otherwise:
Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-10-31 16:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 16:01 [LTP] [PATCH v8 0/4] Automatically generate syscalls.h Andrea Cervesato
2024-10-31 16:01 ` [LTP] [PATCH v8 1/4] Refactor regen.sh script to generate syscalls Andrea Cervesato
2024-10-31 16:21 ` Cyril Hrubis [this message]
2024-11-01 7:39 ` Petr Vorel
2024-11-01 8:07 ` Andrea Cervesato via ltp
2024-10-31 16:01 ` [LTP] [PATCH v8 2/4] Add script to generate arch(s) dependant syscalls Andrea Cervesato
2024-11-01 9:18 ` Petr Vorel
2024-10-31 16:01 ` [LTP] [PATCH v8 3/4] Delete obsolete strip_syscall.awk file Andrea Cervesato
2024-10-31 16:01 ` [LTP] [PATCH v8 4/4] Add documentation about syscalls.h generator Andrea Cervesato
2024-10-31 16:31 ` Cyril Hrubis
2024-11-01 7:56 ` Petr Vorel
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=ZyOucZF2mzL-Jame@yuki.lan \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.de \
--cc=ltp@lists.linux.it \
/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.