lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 14 Jun 2011 15:23:07 +1000 From: Julian Calaby <julian.calaby@...il.com> To: Joe Perches <joe@...ches.com> Cc: netdev@...r.kernel.org, "Luis R. Rodriguez" <lrodriguez@...eros.com>, Jouni Malinen <jmalinen@...eros.com>, Vasanthakumar Thiagarajan <vasanth@...eros.com>, Senthil Balasubramanian <senthilkumar@...eros.com>, "John W. Linville" <linville@...driver.com>, Christian Lamparter <chunkeey@...glemail.com>, Stanislaw Gruszka <sgruszka@...hat.com>, Wey-Yi Guy <wey-yi.w.guy@...el.com>, Intel Linux Wireless <ilw@...ux.intel.com>, linux-wireless@...r.kernel.org, ath9k-devel@...ts.ath9k.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH net-next 1/2] wireless: Remove casts of void * Joe, On Tue, Jun 14, 2011 at 14:02, Joe Perches <joe@...ches.com> wrote: > Unnecessary casts of void * clutter the code. > > These are the remainder casts after several specific > patches to remove netdev_priv and dev_priv. You seem to have removed a lot of casts that don't relate to these cleanups. In particular, some of the casts seem to relate more to documentation rather than just changing pointer types to make the compiler happy. In particular, I'm referring to the casts describing the different usages of data_buf in mwiflex, and around some pointer math in ath9k. Whilst I'm sure that the compiler is smart enough to handle automatic casts between pointer types, some of these, in particular the mwiflex bits, add some documentation to the code. Thanks, -- Julian Calaby Email: julian.calaby@...il.com Profile: http://www.google.com/profiles/julian.calaby/ .Plan: http://sites.google.com/site/juliancalaby/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists