From: Jakub Kicinski <kuba@kernel.org>
To: Felix Maurer <fmaurer@redhat.com>
Cc: socketcan@hartkopp.net, mkl@pengutronix.de, shuah@kernel.org,
davem@davemloft.net, edumazet@google.com, 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:02:02 -0700 [thread overview]
Message-ID: <20250424160202.52472f66@kernel.org> (raw)
In-Reply-To: <cover.1745323279.git.fmaurer@redhat.com>
On Tue, 22 Apr 2025 14:02:33 +0200 Felix Maurer wrote:
> I have cc'ed netdev and its reviewers and maintainers to make sure they
> are okay with the location of the tests and the changes to the paths in
> MAINTAINERS. The changes should be merged through linux-can-next and
> subsequent changes will not go to netdev anymore.
Makes perfect sense to me as well, FWIW.
prev parent reply other threads:[~2025-04-24 23:02 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
2025-04-24 15:19 ` Vincent Mailhol
2025-04-24 23:02 ` Jakub Kicinski [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=20250424160202.52472f66@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=edumazet@google.com \
--cc=fmaurer@redhat.com \
--cc=fstornio@redhat.com \
--cc=horms@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).