From: Petr Vorel <pvorel@suse.cz>
To: Teo Couprie Diaz <teo.coupriediaz@arm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] syscalls/brk: add direct syscall tst_variant
Date: Tue, 13 Dec 2022 20:00:07 +0100 [thread overview]
Message-ID: <Y5jLt3e3xODIcj8d@pevik> (raw)
In-Reply-To: <a2f0fa00-f14f-e394-c5cb-f2916cdc1271@arm.com>
Hi Teo,
...
> > Looking on extra brk() support detection, you must have tested it on Alpine.
> > What am I missing?
> That is quite strange indeed. As Richard pointed out in his reply to this
> message, those warnings should not happen anymore since my patch that
> changed tst_syscall to use intptr_t. ( e5d2a05a90e5 : regen.sh: Use intptr_t
> for tst_syscall return )
> However, I believe that the relevant header is only regenerated when running
> ./configure , not when building normally. I know that I forgot to do it a
> few times myself while testing the change to tst_syscall !
> To be sure that it is supposed to work, I did the following on an Alpine VM
> I used for testing :
> make clean
> make autotools
> ./configure
I'm sorry to forget basic LTP things. Setup was really old, thus rerunning
configure was needed.
No more objections from my side, merged with changes I previously posted
(to keep checks happy).
Thank you!
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-12-13 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 9:24 [LTP] [PATCH v2] syscalls/brk: add direct syscall tst_variant Teo Couprie Diaz
2022-12-12 15:12 ` Richard Palethorpe
2022-12-12 15:22 ` Petr Vorel
2022-12-12 18:28 ` Teo Couprie Diaz
2022-12-12 19:28 ` Petr Vorel
2022-12-13 9:34 ` Richard Palethorpe
2022-12-13 11:48 ` Teo Couprie Diaz
2022-12-13 19:00 ` Petr Vorel [this message]
2022-12-14 10:03 ` Teo Couprie Diaz
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=Y5jLt3e3xODIcj8d@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=teo.coupriediaz@arm.com \
/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.