From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2 1/3] lib: adding .arch field in tst_test structure
Date: Wed, 3 Nov 2021 15:10:15 +0100 [thread overview]
Message-ID: <YYKYR4kspdlXuoDB@yuki> (raw)
In-Reply-To: <CAEemH2fDxJ1xQ9qNejHDxv0p_Cx2cq5LsXTesuhAEBrDe43Hmg@mail.gmail.com>
Hi!
> Um, I can't recall why the V3 development for .arch
> was suspended.
>
> Maybe we thought there is not much sense to replace
> ifdef __arch__ from code at that moment.
>
> Now, if that can benefit the tst_test metadata more in the next runltp-ng.
> Should we keep going to work out the patch V3?
>
> @Cyril Hrubis <chrubis@suse.cz> any suggestions?
Hmm, I guess that I said that it still makes to add the metadata, at
least array of supported architectures in the test_test structure would
be a good addition.
However the hard part would be keeping the actual code and metadata in
sync, we still have to keep the ifdefs in the code.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-11-03 14:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-15 4:20 [LTP] [PATCH v2 1/3] lib: adding .arch field in tst_test structure Li Wang
2019-06-15 4:20 ` [LTP] [PATCH v2 2/3] testcase: taking use of .arch in tst_test Li Wang
2019-06-17 21:49 ` Petr Vorel
2019-06-15 4:20 ` [LTP] [PATCH v2 3/3] testcase: get rid of compiling errors Li Wang
2019-06-17 21:42 ` Petr Vorel
2019-06-17 21:44 ` Jan Stancek
2019-06-18 4:03 ` Li Wang
2019-06-17 21:46 ` [LTP] [PATCH v2 1/3] lib: adding .arch field in tst_test structure Petr Vorel
2019-06-18 2:53 ` Li Wang
2019-06-17 21:49 ` Petr Vorel
2019-06-18 3:07 ` Li Wang
2019-06-18 5:51 ` Petr Vorel
2021-11-03 12:00 ` Richard Palethorpe
2021-11-03 14:03 ` Li Wang
2021-11-03 14:10 ` Cyril Hrubis [this message]
2021-11-04 10:18 ` Li Wang
2021-11-04 10:26 ` Cyril Hrubis
2021-11-05 9:47 ` Richard Palethorpe
2021-11-05 13:23 ` Li Wang
2021-11-05 13:55 ` Richard Palethorpe
2021-11-05 14:22 ` Cyril Hrubis
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=YYKYR4kspdlXuoDB@yuki \
--to=chrubis@suse.cz \
--cc=liwang@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox