Wireless Daemon for Linux
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: [PATCH 06/11] manager: utilize IWD_MODULE
Date: Fri, 11 Oct 2019 13:57:48 -0500	[thread overview]
Message-ID: <2e468dc6-bc20-4109-c205-0697a4bb2e23@gmail.com> (raw)
In-Reply-To: <20191011172417.23328-6-prestwoj@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]

Hi James,

On 10/11/19 12:24 PM, James Prestwood wrote:
> Converts manager into an IWD module. Two getters needed to be added so
> manager can get the white/black list of interfaces.

Can we split this up into two commits please.  One for the getter 
refactoring and one for the module migration.

> ---
>   src/iwd.h     |  5 ++---
>   src/main.c    | 13 ++++++++++---
>   src/manager.c | 26 ++++++++++++++++++--------
>   3 files changed, 30 insertions(+), 14 deletions(-)
> 
> diff --git a/src/iwd.h b/src/iwd.h
> index 7ae7e4b4..8814c244 100644
> --- a/src/iwd.h
> +++ b/src/iwd.h
> @@ -30,9 +30,8 @@ struct l_genl *iwd_get_genl(void);
>   
>   void netdev_shutdown(void);
>   
> -bool manager_init(struct l_genl_family *in,
> -			const char *if_whitelist, const char *if_blacklist);
> -void manager_exit(void);
> +const char *iwd_get_iface_whitelist(void);
> +const char *iwd_get_iface_blacklist(void);

Don't we also have phy lists?  Ah I guess you take care of this in the 
next patch...

>   
>   struct iwd_module_desc {
>   	const char *name;

<snip>

> @@ -637,10 +639,15 @@ bool manager_init(struct l_genl_family *in,
>   	if (randomize_str && !strcmp(randomize_str, "once"))
>   		randomize = true;
>   
> -	return true;
> +	return 0;
> +
> +error:
> +	l_queue_destroy(pending_wiphys, NULL);
> +	l_genl_family_free(nl80211);

Maybe reset nl80211 to NULL just to be pedantic

> +	return -EIO;
>   }
>   
> -void manager_exit(void)
> +static void manager_exit(void)
>   {
>   	l_strfreev(whitelist_filter);
>   	l_strfreev(blacklist_filter);

Regards,
-Denis

  reply	other threads:[~2019-10-11 18:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11 17:24 [PATCH 01/11] main: move module init into nl80211_appeared James Prestwood
2019-10-11 17:24 ` [PATCH 02/11] netdev: utilize IWD_MODULE James Prestwood
2019-10-11 17:24 ` [PATCH 03/11] eapol: " James Prestwood
2019-10-11 17:24 ` [PATCH 04/11] anqp: " James Prestwood
2019-10-11 17:24 ` [PATCH 05/11] agent: " James Prestwood
2019-10-11 18:53   ` Denis Kenzior
2019-10-11 17:24 ` [PATCH 06/11] manager: " James Prestwood
2019-10-11 18:57   ` Denis Kenzior [this message]
2019-10-11 17:24 ` [PATCH 07/11] wiphy: " James Prestwood
2019-10-11 17:24 ` [PATCH 08/11] eap: remove mtu argument from eap_init James Prestwood
2019-10-11 17:24 ` [PATCH 09/11] wired: update with new eap_init James Prestwood
2019-10-11 17:24 ` [PATCH 10/11] unit: update wsc/eapol " James Prestwood
2019-10-11 17:24 ` [PATCH 11/11] eap: utilize IWD_MODULE James Prestwood

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=2e468dc6-bc20-4109-c205-0697a4bb2e23@gmail.com \
    --to=denkenz@gmail.com \
    --cc=iwd@lists.01.org \
    /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