linux-kernel - Re: [PATCH] staging: wilc1000: use kmemdup to replace kmalloc/memcpy

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 14 Mar 2018 12:38:18 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     hariprasath.elango@...il.com
Cc:     aditya.shankar@...rochip.com, ganesh.krishna@...rochip.com,
        devel@...verdev.osuosl.org, linux-wireless@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: wilc1000: use kmemdup to replace kmalloc/memcpy

On Tue, Mar 13, 2018 at 06:19:32PM +0530, hariprasath.elango@...il.com wrote:
> From: HariPrasath Elango <hariprasath.elango@...il.com>
> 
> kmalloc followed by memcpy can be replaced by kmemdup.Also added the
> related error handling part
> 
> Signed-off-by: HariPrasath Elango <hariprasath.elango@...il.com>
> ---
>  drivers/staging/wilc1000/host_interface.c | 10 +++++++---
>  1 file changed, 7 insertions(+), 3 deletions(-)

You have sent at least 8 patches for this driver over the past day, yet
I have no idea what order to apply these in at all.

Please resend them all as a proper patch series, numbered so I have a
clue as to what order to apply them in.  Also preserve the acks/reviews
that others have provided so they don't have to provide that again.

thanks,

greg k-h