From: Hangbin Liu <liuhangbin@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, "Donald Hunter" <donald.hunter@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Jan Stancek" <jstancek@redhat.com>,
"Matthieu Baerts (NGI0)" <matttbe@kernel.org>,
"Asbjørn Sloth Tønnesen" <ast@fiberby.net>,
"Stanislav Fomichev" <sdf@fomichev.me>,
"Ido Schimmel" <idosch@nvidia.com>,
"Guillaume Nault" <gnault@redhat.com>,
"Petr Machata" <petrm@nvidia.com>
Subject: Re: [PATCHv2 net-next 3/3] tools: ynl: add YNL test framework
Date: Mon, 10 Nov 2025 03:14:45 +0000 [thread overview]
Message-ID: <aRFYpTAnlvnobQN1@fedora> (raw)
In-Reply-To: <20251106064512.086e9cb9@kernel.org>
On Thu, Nov 06, 2025 at 06:45:12AM -0800, Jakub Kicinski wrote:
> > > And how would we run all the tests in the new directory?
> > >
> > > Since we have two test files we need some way to run all.
> >
> > I didn't get your requirement. We can run them one by one in the test folder.
> >
> > # ./test_ynl_cli.sh
> > # ./test_ynl_ethtool.sh
> >
> > Do you want to use a wrapper to run the 2 tests? e.g.
> > # ./run_all_ynl_tests.sh
>
> Or make run_tests, like ksft
OK, makes sense to me.
Hangbin
prev parent reply other threads:[~2025-11-10 3:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 8:28 [PATCHv2 net-next 0/3] Add YNL test framework and library improvements Hangbin Liu
2025-11-05 8:28 ` [PATCHv2 net-next 1/3] tools: ynl: Add MAC address parsing support Hangbin Liu
2025-11-05 8:28 ` [PATCHv2 net-next 2/3] netlink: specs: update rt-rule src/dst attribute types to support IPv4 addresses Hangbin Liu
2025-11-05 8:28 ` [PATCHv2 net-next 3/3] tools: ynl: add YNL test framework Hangbin Liu
2025-11-05 17:00 ` Sabrina Dubroca
2025-11-06 1:39 ` Hangbin Liu
2025-11-06 2:33 ` Jakub Kicinski
2025-11-06 2:40 ` Hangbin Liu
2025-11-06 14:45 ` Jakub Kicinski
2025-11-10 3:14 ` Hangbin Liu [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=aRFYpTAnlvnobQN1@fedora \
--to=liuhangbin@gmail.com \
--cc=ast@fiberby.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jstancek@redhat.com \
--cc=kuba@kernel.org \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=sdf@fomichev.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.