All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: [PATCH 1/3] ap: Drop struct ap_config in favor of l_settings
Date: Wed, 28 Apr 2021 11:26:13 -0500	[thread overview]
Message-ID: <b9f63d9b-616f-eb45-c7a4-c6442cc04741@gmail.com> (raw)
In-Reply-To: <20210426233408.775576-1-andrew.zaborowski@intel.com>

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

Hi Andrew,

On 4/26/21 6:34 PM, Andrew Zaborowski wrote:
> Change ap_start to load all of the AP configuration from a struct
> l_settings, moving the 6 or so parameters from struct ap_config members
> to the l_settings groups and keys.  This extends the ap profile concept
> used for the DHCP settings.  ap_start callers create the l_settings
> object and fill the values in it or read the settings in from a file.
> 
> Since ap_setup_dhcp and ap_load_profile_and_dhcp no longer do the
> settings file loading, they needed to be refactored and some issues were
> fixed in their logic, e.g. l_dhcp_server_set_ip_address() was never
> called when the "IP pool" was used.  Also the IP pool was previously only
> used if the ap->config->profile was NULL and this didn't match what the
> docs said:
> "If [IPv4].Address is not provided and no IP address is set on the
> interface prior to calling StartProfile the IP pool will be used."
> ---
>   src/ap.c  | 547 ++++++++++++++++++++++++++++++++----------------------
>   src/ap.h  |  19 +-
>   src/p2p.c |  53 ++++--
>   3 files changed, 359 insertions(+), 260 deletions(-)
> 

All applied, thanks.

Regards,
-Denis

      parent reply	other threads:[~2021-04-28 16:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 23:34 [PATCH 1/3] ap: Drop struct ap_config in favor of l_settings Andrew Zaborowski
2021-04-26 23:34 ` [PATCH 2/3] doc: Clarify settings in iwd.ap(5) Andrew Zaborowski
2021-04-26 23:34 ` [PATCH 3/3] doc: Update iwd.ap(5) man page Andrew Zaborowski
2021-04-28 16:26 ` 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=b9f63d9b-616f-eb45-c7a4-c6442cc04741@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 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.