From: zhong jiang <zhongjiang@huawei.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: <linux-kernel@vger.kernel.org>, Fuqian Huang <huangfq.daxian@gmail.com>
Subject: Re: [PATCH] fs: omfs: Use kmemdup rather than duplicating its implementation in omfs_get_imap
Date: Tue, 3 Sep 2019 21:57:50 +0800 [thread overview]
Message-ID: <5D6E715E.2070602@huawei.com> (raw)
In-Reply-To: <20190903132532.GB5280@localhost>
On 2019/9/3 21:25, Bob Copeland wrote:
> On Tue, Sep 03, 2019 at 02:39:44PM +0800, zhong jiang wrote:
>> kmemdup contains the kmalloc + memcpy. hence it is better to use kmemdup
>> directly. Just replace it.
>>
>> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
> This same patch was already sent to me by someone else and I acked it:
>
> https://lore.kernel.org/lkml/20190703163158.937-1-huangfq.daxian@gmail.com/
>
I miss the patch. Thanks,
Sincerely,
zhong jiang
prev parent reply other threads:[~2019-09-03 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 6:39 [PATCH] fs: omfs: Use kmemdup rather than duplicating its implementation in omfs_get_imap zhong jiang
2019-09-03 13:25 ` Bob Copeland
2019-09-03 13:57 ` zhong jiang [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=5D6E715E.2070602@huawei.com \
--to=zhongjiang@huawei.com \
--cc=huangfq.daxian@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=me@bobcopeland.com \
/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;
as well as URLs for NNTP newsgroup(s).