From: Jakub Kicinski <kuba@kernel.org>
To: Jeremy Kerr <jk@codeconstruct.com.au>
Cc: netdev@vger.kernel.org, Matt Johnston <matt@codeconstruct.com.au>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
David Howells <dhowells@redhat.com>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Liang Chen <liangchen.linux@gmail.com>,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH net-next 10/11] net: mctp: tests: Test that outgoing skbs have flow data populated
Date: Fri, 16 Feb 2024 06:23:04 -0800 [thread overview]
Message-ID: <20240216062304.2c3428d9@kernel.org> (raw)
In-Reply-To: <73b3194049ea75649cc22c17f7d11fa6f9487894.1708071380.git.jk@codeconstruct.com.au>
On Fri, 16 Feb 2024 16:19:20 +0800 Jeremy Kerr wrote:
> +static void mctp_test_packet_flow(struct kunit *test)
> +{
> + kunit_skip(test, "Requires CONFIG_MCTP_FLOWS=y");
> +}
> +
> +static void mctp_test_fragment_flow(struct kunit *test)
> +{
> + kunit_skip(test, "Requires CONFIG_MCTP_FLOWS=y");
> +}
These two get skipped when running:
./tools/testing/kunit/kunit.py run --alltests
Is it possible to make all-test include the right config option
automatically, so they can run?
next prev parent reply other threads:[~2024-02-16 14:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 8:19 [PATCH net-next 00/11] MCTP core protocol updates, minor fixes & tests Jeremy Kerr
2024-02-16 8:19 ` [PATCH net-next 01/11] net: mctp: avoid confusion over local/peer dest/source addresses Jeremy Kerr
2024-02-16 8:19 ` [PATCH net-next 02/11] net: mctp: Add some detail on the key allocation implementation Jeremy Kerr
2024-02-16 8:19 ` [PATCH net-next 03/11] net: mctp: make key lookups match the ANY address on either local or peer Jeremy Kerr
2024-02-16 8:19 ` [PATCH net-next 04/11] net: mctp: tests: create test skbs with the correct net and device Jeremy Kerr
2024-02-16 8:19 ` [PATCH net-next 05/11] net: mctp: separate key correlation across nets Jeremy Kerr
2024-02-16 8:19 ` [PATCH net-next 06/11] net: mctp: provide a more specific tag allocation ioctl Jeremy Kerr
2024-02-19 8:22 ` Dan Carpenter
2024-02-19 9:48 ` Jeremy Kerr
2024-02-16 8:19 ` [PATCH net-next 07/11] net: mctp: tests: Add netid argument to __mctp_route_test_init Jeremy Kerr
2024-02-16 8:19 ` [PATCH net-next 08/11] net: mctp: tests: Add MCTP net isolation tests Jeremy Kerr
2024-02-16 8:19 ` [PATCH net-next 09/11] net: mctp: copy skb ext data when fragmenting Jeremy Kerr
2024-02-16 8:19 ` [PATCH net-next 10/11] net: mctp: tests: Test that outgoing skbs have flow data populated Jeremy Kerr
2024-02-16 14:23 ` Jakub Kicinski [this message]
2024-02-17 3:32 ` Jeremy Kerr
2024-02-16 8:19 ` [PATCH net-next 11/11] net: mctp: tests: Add a test for proper tag creation on local output Jeremy Kerr
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=20240216062304.2c3428d9@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=johannes.berg@intel.com \
--cc=liangchen.linux@gmail.com \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 NNTP newsgroup(s).