[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e6ce8bb1-dad3-a88c-89e6-f3d0c5ced1f7@users.sourceforge.net>
Date: Mon, 13 Feb 2017 10:50:53 +0100
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Dennis Dalessandro <dennis.dalessandro@...el.com>,
linux-rdma@...r.kernel.org, Doug Ledford <dledford@...hat.com>,
Hal Rosenstock <hal.rosenstock@...il.com>,
"Michael J. Ruhl" <michael.j.ruhl@...el.com>,
Mike Marciniszyn <mike.marciniszyn@...el.com>,
Sean Hefty <sean.hefty@...el.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH 27/27] IB/hfi1: Code reuse with memdup_copy
> Thanks for the patch, but this one is already taken care of along with other similar uses of kmalloc/copy:
> http://marc.info/?l=linux-rdma&m=148656088729538&w=2
Thanks for your information.
The shown source code is reasonable in the update step “[PATCH 27/27] IB/hfi1:
Code reuse with memdup_copy”.
https://patchwork.kernel.org/patch/9562565/
https://lkml.kernel.org/r/<20170208132830.16442.93943.stgit@...m10.sc.intel.com>
I find the commit subject and message partly inappropriate.
How do you think about to mention other function names there?
Regards,
Markus
Powered by blists - more mailing lists