From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH v3 1/3] netdev: move GETLINK into its own function, track command ID
Date: Mon, 19 Jun 2023 20:25:31 -0500 [thread overview]
Message-ID: <1d6dc32a-7576-3e78-ad35-51d1ff3eda73@gmail.com> (raw)
In-Reply-To: <20230619180922.231506-1-prestwoj@gmail.com>
Hi James,
On 6/19/23 13:09, James Prestwood wrote:
> Move this logic into its own function and track the command ID
> so it can be canceled in case of netdev going down.
> ---
> src/netdev.c | 51 +++++++++++++++++++++++++++++++++------------------
> 1 file changed, 33 insertions(+), 18 deletions(-)
>
> v3:
> * Zero get_link_cmd_id in callback
>
All applied, thanks.
Regards,
-Denis
prev parent reply other threads:[~2023-06-20 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 18:09 [PATCH v3 1/3] netdev: move GETLINK into its own function, track command ID James Prestwood
2023-06-19 18:09 ` [PATCH v3 2/3] netdev: disable power save if required James Prestwood
2023-06-19 18:09 ` [PATCH v3 3/3] wiphy: remove l_info's for control port/power save James Prestwood
2023-06-20 1:25 ` 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=1d6dc32a-7576-3e78-ad35-51d1ff3eda73@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).