From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:46194 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727319AbfKFSao (ORCPT ); Wed, 6 Nov 2019 13:30:44 -0500 Received: from pps.filterd (m0098394.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id xA6IUarn107626 for ; Wed, 6 Nov 2019 13:30:43 -0500 Received: from e06smtp02.uk.ibm.com (e06smtp02.uk.ibm.com [195.75.94.98]) by mx0a-001b2d01.pphosted.com with ESMTP id 2w41webtw1-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 06 Nov 2019 13:30:38 -0500 Received: from localhost by e06smtp02.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 6 Nov 2019 18:30:24 -0000 Subject: Re: s390/pkey: Use memdup_user() rather than duplicating its implementation References: <08422b7e-2071-ee52-049e-c3ac55bc67a9@web.de> <6137855bb4170c438c7436cbdb7dfd21639a8855.camel@perches.com> <4fa0e106-2565-8610-1356-4adfba08c0a0@web.de> From: Christian Borntraeger Date: Wed, 6 Nov 2019 19:30:19 +0100 MIME-Version: 1.0 In-Reply-To: <4fa0e106-2565-8610-1356-4adfba08c0a0@web.de> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 8bit Message-Id: Sender: linux-s390-owner@vger.kernel.org List-ID: To: Markus Elfring , Joe Perches , linux-s390@vger.kernel.org, kernel-janitors@vger.kernel.org Cc: Harald Freudenberger , Heiko Carstens , Ingo Franzki , Vasily Gorbik , LKML On 06.11.19 14:00, Markus Elfring wrote: >>> Reuse existing functionality from memdup_user() instead of keeping >>> duplicate source code. >>> >>> Generated by: scripts/coccinelle/api/memdup_user.cocci > … >>> Fixes: f2bbc96e7cfad3891b7bf9bd3e566b9b7ab4553d ("s390/pkey: add CCA AES cipher key support") >> >> This doesn't fix anything > > How would you categorise the proposed source code reduction and software reuse? Cleanup. Can you please stop arguing about review feedback that is clearly right? This is not fixing anything. The Fixes tag is used to decide if something needs a backport. And every backport has a chance for a regression. So adding a Fixes tag to something that is not fixing a bug is actually hurting.