>>> "closed" is rather misleading, since you most certainly should *not* >do >>> dev_close() [and don't, but how should I know reading the commit >log?] >>> >>> johannes >>> >> >> Yes, I see. >> I meant that actually stop_ap leaves device in state similar to >ndo_stop, >> where it is non operational. >> >> Would you suggest better wording? "Inactive", "down", "non >operational" >> or something else? > >Isn't "down" good enough here? So can I change it to: Well that kinda proves my point - down is wrong. Carrier turned off is probably the right thing to do here. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
- [PATCH 5/5] wil6210: update FW file name Vladimir Kondratiev
- Re: [PATCH 5/5] wil6210: update FW file name Kalle Valo
- Re: [PATCH 5/5] wil6210: update FW file name Vladimir Kondratiev
- Re: [PATCH 5/5] wil6210: update FW file n... Kalle Valo
- [PATCH 1/5] wil6210: fw debug mode Vladimir Kondratiev
- [PATCH 2/5] wil6210: debug [add|del]_key operations Vladimir Kondratiev
- [PATCH 4/5] wil6210: stop_ap to leave interface closed Vladimir Kondratiev
- Re: [PATCH 4/5] wil6210: stop_ap to leave interfa... Johannes Berg
- Re: [PATCH 4/5] wil6210: stop_ap to leave int... Vladimir Kondratiev
- Re: [PATCH 4/5] wil6210: stop_ap to leave... Kalle Valo
- Re: [PATCH 4/5] wil6210: stop_ap to l... Johannes Berg
- Re: [PATCH 4/5] wil6210: stop_ap... Kalle Valo
- [PATCH 3/5] wil6210: trace disconnect source Vladimir Kondratiev
