public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Copeland <me@bobcopeland.com>
To: Alex Dewar <alex.dewar90@gmail.com>
Cc: linux-karma-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: omfs: use kmemdup() rather than kmalloc+memcpy
Date: Mon, 14 Sep 2020 09:03:44 -0400	[thread overview]
Message-ID: <20200914130344.GA4515@bobcopeland.com> (raw)
In-Reply-To: <5efaa7be-1890-0169-d133-8dd40b238d6d@gmail.com>

On Wed, Sep 09, 2020 at 08:04:15PM +0100, Alex Dewar wrote:
> On 24/08/2020 22:17, Alex Dewar wrote:
> > Issue identified with Coccinelle.
> Gentle ping?
> > 
> > Signed-off-by: Alex Dewar <alex.dewar90@gmail.com>

Acked-by: Bob Copeland <me@bobcopeland.com>

However, I don't have a git tree for OMFS so you'll need to send it
through vfs tree or so.

-- 
Bob Copeland %% https://bobcopeland.com/

      reply	other threads:[~2020-09-14 13:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 21:17 [PATCH] fs: omfs: use kmemdup() rather than kmalloc+memcpy Alex Dewar
2020-09-09 19:04 ` Alex Dewar
2020-09-14 13:03   ` Bob Copeland [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=20200914130344.GA4515@bobcopeland.com \
    --to=me@bobcopeland.com \
    --cc=alex.dewar90@gmail.com \
    --cc=linux-karma-devel@lists.sourceforge.net \
    --cc=linux-kernel@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