Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 16 Sep 2019 22:43:35 +0530
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
Message-ID: <20190916171335.GB4060@SD>
References: <20190913171134.GA10301@SD>
 <4fd20946-b991-0c0f-975e-ef79b433912b@web.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4fd20946-b991-0c0f-975e-ef79b433912b@web.de>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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