All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
To: Daniel Wagner <wagi@monom.org>
Cc: HENRIET Vivien <vivien.henriet@overkiz.com>,
	 "connman@lists.linux.dev" <connman@lists.linux.dev>
Subject: Re: [PATCH] wifi: Choose a random channel when opening an ap
Date: Mon, 4 Oct 2021 23:21:09 +0200	[thread overview]
Message-ID: <CAOf5uw=dsGdFmSEBhhQBFY0CkUuAcky=YhouHaOa2zHnaVNE0g@mail.gmail.com> (raw)
In-Reply-To: <6f009b7c-d7ef-6800-f0d8-67f045d6ae4f@monom.org>

Hi

On Mon, Oct 4, 2021 at 9:46 AM Daniel Wagner <wagi@monom.org> wrote:
>
> On 04.10.21 09:34, Michael Nazzareno Trimarchi wrote:
> > I can create a function to get
> >
> > ident = technology->tethering_ident;
> > passphrase = technology->tethering_passphrase;
> > freq = technology->tethering_freq;
> >
> > connman_tethering_get_params(techonology, &ident, &passphrase, &freq);
>
> Yes, that is what I had in mind. We need to retrieve these values from
> the core/config somehow.

I send an RFC in the mailing list just rebase some old patch and
adjust a bit to be more complete. I did not
time to test. I need to know if it can be a starting point or not.

Michael


-- 
Michael Nazzareno Trimarchi
Co-Founder & Chief Executive Officer
M. +39 347 913 2170
michael@amarulasolutions.com
__________________________________

Amarula Solutions BV
Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
T. +31 (0)85 111 9172
info@amarulasolutions.com
www.amarulasolutions.com

      reply	other threads:[~2021-10-04 21:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23 12:44 [PATCH] wifi: Choose a random channel when opening an ap Vivien Henriet
2021-09-29  8:57 ` HENRIET Vivien
2021-09-29  9:16   ` Daniel Wagner
2021-10-04  6:45     ` Michael Nazzareno Trimarchi
2021-10-04  7:09       ` Daniel Wagner
2021-10-04  7:34         ` Michael Nazzareno Trimarchi
2021-10-04  7:46           ` Daniel Wagner
2021-10-04 21:21             ` Michael Nazzareno Trimarchi [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='CAOf5uw=dsGdFmSEBhhQBFY0CkUuAcky=YhouHaOa2zHnaVNE0g@mail.gmail.com' \
    --to=michael@amarulasolutions.com \
    --cc=connman@lists.linux.dev \
    --cc=vivien.henriet@overkiz.com \
    --cc=wagi@monom.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.