* nl80211 data prior to nested attributes funky
@ 2009-03-20 1:05 Luis R. Rodriguez
2009-03-20 8:24 ` Johannes Berg
0 siblings, 1 reply; 2+ messages in thread
From: Luis R. Rodriguez @ 2009-03-20 1:05 UTC (permalink / raw)
To: linux-wireless@vger.kernel.org; +Cc: Johannes Berg, pat-lkml
If you try to rename a wiphy multiple times with iw you will get
something like this:
wiphy rename: phy #1 to 2
wiphy rename: phy #1 to 3
This just shows an example of an issue I am seeing with another
multicast message I'm working on. I thought it was my code but I've
asked Pat to test and he also saw it. I'd dig more but I have am going
to work on fixing the cfg80211 reg oops with "EU" now.
Luis
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: nl80211 data prior to nested attributes funky
2009-03-20 1:05 nl80211 data prior to nested attributes funky Luis R. Rodriguez
@ 2009-03-20 8:24 ` Johannes Berg
0 siblings, 0 replies; 2+ messages in thread
From: Johannes Berg @ 2009-03-20 8:24 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: linux-wireless@vger.kernel.org, pat-lkml
On Thu, 2009-03-19 at 18:05 -0700, Luis R. Rodriguez wrote:
> If you try to rename a wiphy multiple times with iw you will get
> something like this:
>
> wiphy rename: phy #1 to 2
> wiphy rename: phy #1 to 3
I don't see any error?
# iw phy phy0 set name falafel
# iw phy falafel set name guacamole
# iw phy guacamole set name phy1
command failed: Invalid argument (-22)
# iw phy guacamole set name phy0
where I will get in iw event:
$ iw event
wiphy rename: phy #0 to falafel
wiphy rename: phy #0 to guacamole
wiphy rename: phy #0 to phy0
were you expecting the old name, rather than the index?
johannes
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-03-20 8:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-03-20 1:05 nl80211 data prior to nested attributes funky Luis R. Rodriguez
2009-03-20 8:24 ` Johannes Berg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox