All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH iw] add "channels" PHY command listing frequencies with more details
Date: Tue, 31 May 2016 15:14:47 +0200	[thread overview]
Message-ID: <1464700487.3076.28.camel@sipsolutions.net> (raw)
In-Reply-To: <CACna6rw--bPNdWcp1Bx1GOKv9cnOgfr5D_YU1RF7A8CS_Bt7Vg@mail.gmail.com> (sfid-20160531_151009_650354_316F309E)

On Tue, 2016-05-31 at 15:10 +0200, Rafał Miłecki wrote:

> > Unfortunately, I get compiler warnings about width_* being possibly
> > used uninitialized. Can you address that please?
> It's nice your compiled got this mistake, my didn't. There were
> actually meant to be static. I'll fix that.

I actually think the compiler is wrong, and there's no reason for them
to be static, is there?

The first iteration of the loop should always initialize since -1 is
used for initialization?

In any case, I'd prefer to avoid static, if necessary pass some kind of
context structure in to the function?

> > > +TOPLEVEL(channels, NULL, NL80211_CMD_GET_WIPHY, 0, CIB_PHY,
> > > handle_channels, "Show available channels.");
> > Maybe that should be allowed for a CIB_DEV too?
> Since this is PHY specific, I was thinking it should be CIB_PHY. I
> didn't see reason to allow querying devices. Similarly we don't
> support "iw dev wlan0 reg get".
> 
> Anyway, I can change that if you think it's better for some reason.

I was just thinking that supporting it with wlan0 would in certain
cases make it easier for the user (not having to look up the phy
number)

> Any hint how to make command usable with both: phy and dev?

Just add:

TOPLEVEL(channels, NULL, NL80211_CMD_GET_WIPHY, 0, CIB_NETDEV, ...);

johannes

  reply	other threads:[~2016-05-31 13:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20 10:13 [PATCH iw] add "channels" PHY command listing frequencies with more details Rafał Miłecki
2016-05-31 10:16 ` Johannes Berg
2016-05-31 13:10   ` Rafał Miłecki
2016-05-31 13:14     ` Johannes Berg [this message]
2016-05-31 15:58       ` Rafał Miłecki
2016-05-31 16:20         ` Rafał Miłecki
2016-05-31 16:28 ` [PATCH V2 " Rafał Miłecki
2016-05-31 18:16   ` Johannes Berg
2016-06-01  5:51   ` [PATCH V3 " Rafał Miłecki

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=1464700487.3076.28.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@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.