Wireless Daemon for Linux
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz at gmail.com>
To: iwd at lists.01.org
Subject: Re: [PATCH v2 1/2] hwsim: allow concurrent radio creations
Date: Tue, 15 Feb 2022 13:40:58 -0600	[thread overview]
Message-ID: <6831ecc0-9251-339e-856b-d9d2ac9d669f@gmail.com> (raw)
In-Reply-To: 556a79f1b541f77dc4a7b147935b216170425b49.camel@gmail.com

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

Hi James,

On 2/15/22 13:16, James Prestwood wrote:
> Hi Denis,
> 
>>
>>> +       } else if (!rec)
>>> +               return;
>>
>> This part seems suspicious.  What if the radio is being created
>> outside hwsim?
> 
> I guess this is changing behavior... Currently we would still create
> the radio info object if the radio was created externally. Keeping this
> behavior will end up requiring creating the radio here and in
> CreateRadio(), nearly the same as what we had before.
> 

CreateRadio really only creates a stub.  What is there to duplicate besides 
l_new and setting the name/id?

> I guess its up to you. Either we don't support external radio creation
> for cleaner code, or we go back to the way it was (or some variant of
> it).
> 

Clearly we want to support this since hwsim might start with radios already 
created and this path is being used by the initial radio dump (started in 
hwsim_ready).

Regards,
-Denis

             reply	other threads:[~2022-02-15 19:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 19:40 Denis Kenzior [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-15 19:16 [PATCH v2 1/2] hwsim: allow concurrent radio creations James Prestwood
2022-02-15 17:53 Denis Kenzior
2022-02-15 16:52 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=6831ecc0-9251-339e-856b-d9d2ac9d669f@gmail.com \
    --to=iwd@lists.linux.dev \
    /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