connman.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@monom.org>
To: Michael Trimarchi <michael@amarulasolutions.com>
Cc: connman@lists.linux.dev
Subject: Re: [RFC PATCH] tether: Add a way to define a tethering frequency
Date: Wed, 6 Oct 2021 14:40:43 +0200	[thread overview]
Message-ID: <20211006124043.l7nlcqciqk5wc6ef@carbon.fritz.box> (raw)
In-Reply-To: <20211004210016.1579481-1-michael@amarulasolutions.com>

Hi Michael,

On Mon, Oct 04, 2021 at 11:00:16PM +0200, Michael Trimarchi wrote:
> Add an optional parameter to set the frequency of access point. Need to
> be splitted in multiple patches. This is used as initial idea.

Nice, this is what I had in mind.

> TODO:
> - split

Yes please.

> - add freq constraints
> - move to unsigned int

Daniel

  reply	other threads:[~2021-10-06 12:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 21:00 [RFC PATCH] tether: Add a way to define a tethering frequency Michael Trimarchi
2021-10-06 12:40 ` Daniel Wagner [this message]
2021-10-06 21:55   ` Michael Nazzareno Trimarchi
2021-10-07 15:04     ` Daniel Wagner

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=20211006124043.l7nlcqciqk5wc6ef@carbon.fritz.box \
    --to=wagi@monom.org \
    --cc=connman@lists.linux.dev \
    --cc=michael@amarulasolutions.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).