On Sun, Apr 29, 2018 at 03:23:02PM +0200, Greg KH wrote: > On Fri, Apr 27, 2018 at 04:05:54PM +0200, Sergio Paracuellos wrote: > > Cleanups continues with this patch series. Main changes are > > related with MIB where some preprocessor stuff has been change > > in favour of an enumeration and some helper functions to increase > > code readability has been included. Other changes are minor > > cleanups in different part of code. > > > > Sergio Paracuellos (10): > > staging: ks7010: clean SME_MIC_FAILURE_REQUEST case in > > hostif_sme_execute > > staging: ks7010: convert MIB preprocessor defs into an enum > > staging: ks7010: conver MIB attributes preprocessor defs into an enum > > staging: ks7010: change some casts from uint8_t to u8 in ks_hostif > > header > > staging: ks7010: change parameter types and reorder them in > > hostif_mib_set_request > > staging: ks7010: add new helpers to achieve mib set request and > > simplify code > > staging: ks7010: use ether_addr_copy in get_current_ap > > staging: ks7010: move two preprocessor definitions to ks_wlan.h > > staging: ks7010: avoid two long lines in hostif_sme_mode_setup > > staging: ks7010: remove non sense comments in ks_hostif.c source file > > > > drivers/staging/ks7010/ks_hostif.c | 320 +++++++++++++++++------------------ > > drivers/staging/ks7010/ks_hostif.h | 175 ++++++++++++------- > > drivers/staging/ks7010/ks_wlan.h | 3 + > > drivers/staging/ks7010/ks_wlan_net.c | 4 +- > > 4 files changed, 275 insertions(+), 227 deletions(-) > > I now have 31+ emails from you in my to-review queue. These are > multiple series of patches, yet I have no idea what order they are in at > all. > > Please make it easy on me, make it obvious what to do, and what to apply > in what order. > > I'm dropping all of your emails now, please resend everything I have not > applied, in a _SINGLE_ patch series so I can handle it properly. Ack! I'll resend all of them in one patch series. > > thanks, > > greg k-h Best regards, Sergio Paracuellos _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel