From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH v3 01/13] auto-t: add explicit stop() to IWD class
Date: Wed, 13 Dec 2023 10:14:55 -0600 [thread overview]
Message-ID: <706a7157-9d37-472c-b610-7f0a2c3a69f7@gmail.com> (raw)
In-Reply-To: <20231206201802.2139649-1-prestwoj@gmail.com>
Hi James,
On 12/6/23 14:17, James Prestwood wrote:
> If tests end in an unknown state it is sometimes required that IWD
> be stopped manually in order for future tests to run. Add a stop()
> method so test tearDown() methods can explicitly stop IWD.
> ---
> autotests/util/iwd.py | 4 ++++
> 1 file changed, 4 insertions(+)
>
All applied, thanks.
Regards,
-Denis
prev parent reply other threads:[~2023-12-13 16:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 20:17 [PATCH v3 01/13] auto-t: add explicit stop() to IWD class James Prestwood
2023-12-06 20:17 ` [PATCH v3 02/13] auto-t: add association timeout test James Prestwood
2023-12-06 20:17 ` [PATCH v3 03/13] auto-t: only call set_value for changed values in default() James Prestwood
2023-12-06 20:17 ` [PATCH v3 04/13] handshake: add setters for authenticator/supplicant_fte James Prestwood
2023-12-06 20:17 ` [PATCH v3 05/13] handshake: use authenticator_fte instead of 'fte' James Prestwood
2023-12-06 20:17 ` [PATCH v3 06/13] unit: use authenticator_fte James Prestwood
2023-12-06 20:17 ` [PATCH v3 07/13] handshake: remove handshake_state_set_fte James Prestwood
2023-12-06 20:17 ` [PATCH v3 08/13] ft: add FTE/RSNE building to ft_prepare_handshake James Prestwood
2023-12-06 20:17 ` [PATCH v3 09/13] ft: add ft_handshake_setup James Prestwood
2023-12-06 20:17 ` [PATCH v3 10/13] netdev: add netdev_ft_reassociate James Prestwood
2023-12-06 20:18 ` [PATCH v3 11/13] station: use netdev_ft_reassociate James Prestwood
2023-12-06 20:18 ` [PATCH v3 12/13] ft: remove ft_associate and helpers James Prestwood
2023-12-06 20:18 ` [PATCH v3 13/13] netdev: station: remove NETDEV_EVENT_FT_ROAMED James Prestwood
2023-12-13 16:14 ` Denis Kenzior [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=706a7157-9d37-472c-b610-7f0a2c3a69f7@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=prestwoj@gmail.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