From: Felix Maurer <fmaurer@redhat.com>
To: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Cc: socketcan@hartkopp.net, mkl@pengutronix.de, shuah@kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, linux-can@vger.kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
dcaratti@redhat.com, fstornio@redhat.com
Subject: Re: [PATCH 0/4] selftest: can: Start importing selftests from can-tests
Date: Thu, 24 Apr 2025 16:01:45 +0200 [thread overview]
Message-ID: <c2729303-8ee9-4fe3-9755-2b6d0d0d7b97@redhat.com> (raw)
In-Reply-To: <CAMZ6RqK8TdzzMW645OLq5tbkyQdYW+tGGVcr7vsRBE81_u4W4Q@mail.gmail.com>
On 24.04.25 09:45, Vincent Mailhol wrote:
[...]
>> Felix Maurer (4):
>> selftests: can: Import tst-filter from can-tests
>> selftests: can: use kselftest harness in test_raw_filter
>> selftests: can: Use fixtures in test_raw_filter
>> selftests: can: Document test_raw_filter test cases
>
> You are doing a lot of change to the original to the point that this
> is more a full rewrite. I have no intent of reviewing the first patch
> which is just the copy paste from the original. If no one else has a
> strong opinion on this, I would rather prefer if you just squash
> everything and send a single patch with the final result. This will
> also save you some effort when migrating the other tests.
>
> I have a few comments on the individual patches, but overall very
> good. Thanks a lot!
Thank you very much for your feedback! I'll silently include most of it
and will only reply where I think discussions are necessary.
For squashing / keeping this as individual patches: I usually like to
have some kind of history available, but here it might not provide a lot
of value. I would be fine with squashing as well. If there are any
stronger opinions on this, keep them coming.
Thanks,
Felix
next prev parent reply other threads:[~2025-04-24 14:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 12:02 [PATCH 0/4] selftest: can: Start importing selftests from can-tests Felix Maurer
2025-04-22 12:02 ` [PATCH 1/4] selftests: can: Import tst-filter " Felix Maurer
2025-04-24 7:42 ` Vincent Mailhol
2025-04-24 14:02 ` Felix Maurer
2025-04-24 14:23 ` Vincent Mailhol
2025-04-22 12:02 ` [PATCH 2/4] selftests: can: use kselftest harness in test_raw_filter Felix Maurer
2025-04-24 7:42 ` Vincent Mailhol
2025-04-22 12:02 ` [PATCH 3/4] selftests: can: Use fixtures " Felix Maurer
2025-04-24 7:43 ` Vincent Mailhol
2025-04-22 12:02 ` [PATCH 4/4] selftests: can: Document test_raw_filter test cases Felix Maurer
2025-04-24 7:44 ` Vincent Mailhol
2025-04-24 8:21 ` Vincent Mailhol
2025-04-24 14:02 ` Felix Maurer
2025-04-24 15:08 ` Vincent Mailhol
2025-04-30 9:36 ` Felix Maurer
2025-04-24 7:45 ` [PATCH 0/4] selftest: can: Start importing selftests from can-tests Vincent Mailhol
2025-04-24 14:01 ` Felix Maurer [this message]
2025-04-24 15:19 ` Vincent Mailhol
2025-04-24 23:02 ` Jakub Kicinski
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=c2729303-8ee9-4fe3-9755-2b6d0d0d7b97@redhat.com \
--to=fmaurer@redhat.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=edumazet@google.com \
--cc=fstornio@redhat.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=socketcan@hartkopp.net \
/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