On Mon, Jul 11, 2011 at 10:57:20AM -0500, Larry Finger wrote: > On 07/11/2011 05:07 AM, Ali Bahar wrote: > >These are updates to how the 'bup' flag is handled. The first allows Sets > >before the interface is brought Up, and the second is housekeeping of the > >flag's value when the interface is taken Down. > > > >Ali Bahar (2): > > staging: r8712u: Sets to SSID, and to AP MAC#, can now be done > > when the interface is Down. > > staging: r8712u: Interface-state not fully tracked. > > > > drivers/staging/rtl8712/drv_types.h | 5 +++++ > > drivers/staging/rtl8712/os_intfs.c | 14 ++++++++++++++ > > drivers/staging/rtl8712/rtl871x_ioctl_linux.c | 25 +++++++++++++++++++++---- > > 3 files changed, 40 insertions(+), 4 deletions(-) > > > > Ali, > > The patches look good, except for one problem. As this driver is in > staging, the patches need to be sent to Greg Kroah-Hartman > <gregkh@xxxxxxx>, not through linux-wireless. Hmm, I must admit that I'd raised this question with myself (ie Staging's recipients), and had dug into it a bit, but neglected it at the last minute. Sorry. See below, anyway. > One other point - for those patches that are properly sent through > wireless, John Linville should be the one to receive those. He is > the maintainer for that section, just as GregKH is the maintainer > for staging. Yes, but my understanding was that _you_ are my upstream, since you are this driver's maintainer. (MAINTAINERS does not mention you for exactly the r8712u, but does so for related devices.) So it was going to be To: Larry, CC: wireless ML. Observing other threads suggested that you may then Ack and send it to Linville -- which, now that you have reminded me, would have been Greg KH. OK, so I will re-send these to Greg. Do you not get even a CC?!! You mention none, above, and had offered/expected to review them (in a 3 July email.) (NB I ruled out a CC to linuxdriverproject.org, of course.) thanks, ali -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
