From: "<Hariprasath Elango>" <hariprasath.elango@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: hariprasath.elango@gmail.com, aditya.shankar@microchip.com,
ganesh.krishna@microchip.com, devel@driverdev.osuosl.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: wilc1000: use kmemdup to replace kmalloc/memcpy
Date: Wed, 14 Mar 2018 17:51:07 +0530 [thread overview]
Message-ID: <20180314122107.GA10753@hariprasath> (raw)
In-Reply-To: <20180314113818.GA7169@kroah.com>
On Wed, Mar 14, 2018 at 12:38:18PM +0100, Greg Kroah-Hartman wrote:
> On Tue, Mar 13, 2018 at 06:19:32PM +0530, hariprasath.elango@gmail.com wrote:
> > From: HariPrasath Elango <hariprasath.elango@gmail.com>
> >
> > kmalloc followed by memcpy can be replaced by kmemdup.Also added the
> > related error handling part
> >
> > Signed-off-by: HariPrasath Elango <hariprasath.elango@gmail.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
Hi Greg, thanks. Yes I will send a patchset to make things easier for
you keeping in tact the review history
regards,
hari prasath
prev parent reply other threads:[~2018-03-14 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 12:49 [PATCH] staging: wilc1000: use kmemdup to replace kmalloc/memcpy hariprasath.elango
2018-03-14 11:38 ` Greg Kroah-Hartman
2018-03-14 12:21 ` <Hariprasath Elango> [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180314122107.GA10753@hariprasath \
--to=hariprasath.elango@gmail.com \
--cc=aditya.shankar@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=ganesh.krishna@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox