From: Saiyam Doshi <saiyamdoshi.in@gmail.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Bob Copeland <me@bobcopeland.com>,
linux-karma-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: omfs: make use of kmemdup
Date: Mon, 16 Sep 2019 22:43:35 +0530 [thread overview]
Message-ID: <20190916171335.GB4060@SD> (raw)
In-Reply-To: <4fd20946-b991-0c0f-975e-ef79b433912b@web.de>
On Sat, Sep 14, 2019 at 08:24:37AM +0200, Markus Elfring wrote:
> I suggest to take another look at a similar patch.
>
> fs/omfs: make use of kmemdup
> https://lore.kernel.org/r/20190721112326.GA5927@hari-Inspiron-1545/
> https://lore.kernel.org/patchwork/patch/1102482/
> https://lkml.org/lkml/2019/7/21/40
Oh I missed that. The patch you pointed above is of July, 2019 but I am
not seeing it in v5.3 or in next-20190915.
If you know, can you point to the fs/omfs tree. It will help not to send
repeated change.
-Saiyam
prev parent reply other threads:[~2019-09-16 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 17:11 [PATCH] omfs: make use of kmemdup Saiyam Doshi
2019-09-14 6:24 ` Markus Elfring
2019-09-16 17:13 ` Saiyam Doshi [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=20190916171335.GB4060@SD \
--to=saiyamdoshi.in@gmail.com \
--cc=Markus.Elfring@web.de \
--cc=linux-karma-devel@lists.sourceforge.net \
--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