From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: hariprasad@osuosl.org, Kelam@osuosl.org, hariprasad.kelam@gmail.com
Cc: devel@driverdev.osuosl.org,
Valdis Kletnieks <valdis.kletnieks@vt.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: exfat: make use of kmemdup
Date: Sun, 8 Sep 2019 14:05:40 +0100 [thread overview]
Message-ID: <20190908130540.GA9394@kroah.com> (raw)
In-Reply-To: <1567934921-6475-1-git-send-email-hariprasad.kelam@gmail.com>
On Sun, Sep 08, 2019 at 02:58:41PM +0530, hariprasad@osuosl.org wrote:
> From: Hariprasad Kelam <hariprasad.kelam@gmail.com>
>
> fix below issue reported by coccicheck
> drivers/staging//exfat/exfat_super.c:2709:26-33: WARNING opportunity for
> kmemdup
>
> Signed-off-by: Hariprasad Kelam <hariprasad.kelam@gmail.com>
> ---
> drivers/staging/exfat/exfat_super.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
This doesn't apply to my tree at all, what did you make it against?
thanks,
greg k-h
parent reply other threads:[~2019-09-08 13:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1567934921-6475-1-git-send-email-hariprasad.kelam@gmail.com>]
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=20190908130540.GA9394@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Kelam@osuosl.org \
--cc=devel@driverdev.osuosl.org \
--cc=hariprasad.kelam@gmail.com \
--cc=hariprasad@osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=valdis.kletnieks@vt.edu \
/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