From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 2/4] wiphy: remove nl80211 from wiphy object
Date: Thu, 8 Sep 2022 09:53:44 -0500 [thread overview]
Message-ID: <16a64a4f-5339-e0cd-3fb9-340588cf855d@gmail.com> (raw)
In-Reply-To: <20220907233201.227577-2-prestwoj@gmail.com>
Hi James,
On 9/7/22 18:31, James Prestwood wrote:
> The nl80211 object is already a global and there is no need
> to track this in wiphy itself.
Wiphy is a bit of a weird case since you have a global and a wiphy-specific dump
for regdom. As well as the regdom query. But wouldn't you actually go the
other direction?
l_genl_family_new creates a lightweight handle to the GENL object. Once you
unref this handle, any requests started on this handle are automagically
destroyed. So you strictly speaking do not need to track the command ids
anymore. So for example you could get rid of 'get_reg_id' fairly easily.
'dump_id' is a bit trickier since it is used for conflict detection, but maybe..?
> ---
> src/wiphy.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
Regards,
-Denis
next prev parent reply other threads:[~2022-09-08 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 23:31 [PATCH 1/4] doc: document [General].Country main.conf option James Prestwood
2022-09-07 23:31 ` [PATCH 2/4] wiphy: remove nl80211 from wiphy object James Prestwood
2022-09-08 14:53 ` Denis Kenzior [this message]
2022-09-07 23:32 ` [PATCH 3/4] wiphy: only do global GET_REG once James Prestwood
2022-09-08 15:55 ` Denis Kenzior
2022-09-07 23:32 ` [PATCH 4/4] wiphy: support country code override James Prestwood
2022-09-08 16:00 ` Denis Kenzior
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=16a64a4f-5339-e0cd-3fb9-340588cf855d@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 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.