From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: YunQiang Su <yunqiang.su@cipunited.com>
Cc: YunQiang Su <wzssyqa@gmail.com>, binutils@sourceware.org
Subject: Re: [PATCH v2] GAS/MIPS: Fix testcase module-defer-warn2 for r2+ triples
Date: Fri, 29 Sep 2023 15:32:46 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2309291525210.18635@angie.orcam.me.uk> (raw)
In-Reply-To: <8aee9403-c552-3a42-5be3-1daa1fddea22@cipunited.com>
On Fri, 29 Sep 2023, YunQiang Su wrote:
> > As always one self-contained change per patch please. Switching to the
> > .d format is one change and fixing R2+ support is another. So it has to
> > be two separate changes.
>
>
> To be make thing more clear, and I am worrying that, the patch can be spilt to
> 3 even:
>
> 1. switch to .d format
>
> 2. add "#skip" tag
>
> 3. add new r2 tests.
>
>
> So, if we'd like to split to 2 patches, should they are {{1,2}, 3} or {1, {2,
> 3}}, or should we
>
> split it to 3 ones?
Thanks for raising this point, but I think there is no need to add
"#skip" in a separate step for two reasons:
1. The switch to the .d format preserves the current situation, that is
the test working correctly for R1- and not working correctly for R2+.
There's no need to add "#skip" at this stage.
2. A fix to make the test for R2+ is one functionally self-contained
change and as documented "#skip"/"#noskip" tags are supposed to be used
in pairs (or groups of multiple as required in ternary or wider cases)
to cover variants of one specific test, so having "#skip" with no
corresponding "#noskip" would in fact be incorrect. So it has to be
made in a single change.
I hope I made myself clear here.
Maciej
prev parent reply other threads:[~2023-09-29 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 4:32 [PATCH] " YunQiang Su
2023-08-29 14:46 ` Maciej W. Rozycki
2023-09-26 11:20 ` [PATCH v2] " YunQiang Su
2023-09-28 23:46 ` Maciej W. Rozycki
2023-09-29 13:41 ` YunQiang Su
2023-09-29 14:18 ` Maciej W. Rozycki
2023-09-29 14:23 ` YunQiang Su
2023-09-29 14:32 ` Maciej W. Rozycki [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=alpine.DEB.2.21.2309291525210.18635@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=binutils@sourceware.org \
--cc=wzssyqa@gmail.com \
--cc=yunqiang.su@cipunited.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).