Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Markus Theil <markus.theil@tu-ilmenau.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] nl80211: allow more operations for mesh and ad-hoc interfaces
Date: Wed, 30 Oct 2019 10:03:48 +0100	[thread overview]
Message-ID: <4b9c7b36f175667a76609c6560618bb48a321ed8.camel@sipsolutions.net> (raw)
In-Reply-To: <20191029115602.78990-1-markus.theil@tu-ilmenau.de>

On Tue, 2019-10-29 at 12:56 +0100, Markus Theil wrote:
> This change allows mesh and ad-hoc interfaces to change beacons and
> tx queue settings. The direct change of these settings should be ok
> for these kind of interfaces and should maybe only forbidden for
> station-like interface types.

"should maybe"? :-)

Not really, both of the changes are wrong.

johannes


  reply	other threads:[~2019-10-30  9:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 11:56 [PATCH] nl80211: allow more operations for mesh and ad-hoc interfaces Markus Theil
2019-10-30  9:03 ` Johannes Berg [this message]
2019-10-30 13:40   ` Markus Theil
2019-10-30 14:04     ` Johannes Berg
2019-10-30 14:10       ` Markus Theil

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=4b9c7b36f175667a76609c6560618bb48a321ed8.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=markus.theil@tu-ilmenau.de \
    /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