Home
last modified time | relevance | path

Searched hist:ab8c31dd8c8accea11bd59075bca711579512adc (Results 1 – 3 of 3) sorted by relevance

/openbmc/linux/drivers/net/wireless/st/cw1200/
H A Dqueue.cdiff ab8c31dd8c8accea11bd59075bca711579512adc Wed Jul 03 11:29:34 CDT 2019 Fuqian Huang <huangfq.daxian@gmail.com> net/wireless: Use kmemdup rather than duplicating its implementation

kmemdup is introduced to duplicate a region of memory in a neat way.
Rather than kmalloc/kzalloc + memcpy, which the programmer needs to
write the size twice (sometimes lead to mistakes), kmemdup improves
readability, leads to smaller code and also reduce the chances of mistakes.
Suggestion to use kmemdup rather than using kmalloc/kzalloc + memcpy.

Signed-off-by: Fuqian Huang <huangfq.daxian@gmail.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
/openbmc/linux/drivers/net/wireless/ath/ath6kl/
H A Dwmi.cdiff ab8c31dd8c8accea11bd59075bca711579512adc Wed Jul 03 11:29:34 CDT 2019 Fuqian Huang <huangfq.daxian@gmail.com> net/wireless: Use kmemdup rather than duplicating its implementation

kmemdup is introduced to duplicate a region of memory in a neat way.
Rather than kmalloc/kzalloc + memcpy, which the programmer needs to
write the size twice (sometimes lead to mistakes), kmemdup improves
readability, leads to smaller code and also reduce the chances of mistakes.
Suggestion to use kmemdup rather than using kmalloc/kzalloc + memcpy.

Signed-off-by: Fuqian Huang <huangfq.daxian@gmail.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
/openbmc/linux/drivers/net/wireless/ti/wlcore/
H A Dmain.cdiff ab8c31dd8c8accea11bd59075bca711579512adc Wed Jul 03 11:29:34 CDT 2019 Fuqian Huang <huangfq.daxian@gmail.com> net/wireless: Use kmemdup rather than duplicating its implementation

kmemdup is introduced to duplicate a region of memory in a neat way.
Rather than kmalloc/kzalloc + memcpy, which the programmer needs to
write the size twice (sometimes lead to mistakes), kmemdup improves
readability, leads to smaller code and also reduce the chances of mistakes.
Suggestion to use kmemdup rather than using kmalloc/kzalloc + memcpy.

Signed-off-by: Fuqian Huang <huangfq.daxian@gmail.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>