From: Teo Couprie Diaz <teo.coupriediaz@arm.com>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH 1/1] regen.sh: Use intptr_t for tst_syscall return
Date: Tue, 1 Nov 2022 10:09:07 +0000 [thread overview]
Message-ID: <119655bb-9534-7f83-6203-d6ce260622d6@arm.com> (raw)
In-Reply-To: <Y2AItxvngzUPG8U1@yuki>
Hi,
> Hi!
>> I agree, I wouldn't want to merge it.
>> As mentioned in the cover, I wanted to share the list of tests I have
>> tested the patch with,
>> both for people to test themselves if they want to and as a way to ask
>> if there was anything I missed
>> while testing with that.
>> I didn't really know how to share this, so I added it as part of the
>> commit for the RFC. Maybe it would
>> fit better as part of the cover letter ? Or after the commit description
>> with the shortlog ?
>> It might be better removed altogether and people can test with a larger
>> scope anyway !
> Maybe just a separate patch with [DO NOT MERGE] in the tittle?
That does make sense, I will split it as such when sending the non-RFC
version.
Thanks for the guidance !
Best regards,
Téo Couprie Diaz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-11-01 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 16:36 [LTP] [RFC PATCH 0/1] Change return type of tst_syscall Teo Couprie Diaz
2022-10-27 16:36 ` [LTP] [RFC PATCH 1/1] regen.sh: Use intptr_t for tst_syscall return Teo Couprie Diaz
2022-10-31 13:32 ` Cyril Hrubis
2022-10-31 17:18 ` Teo Couprie Diaz
2022-10-31 17:41 ` Cyril Hrubis
2022-11-01 10:09 ` Teo Couprie Diaz [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=119655bb-9534-7f83-6203-d6ce260622d6@arm.com \
--to=teo.coupriediaz@arm.com \
--cc=chrubis@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).