All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Markus Elfring <Markus.Elfring@web.de>,
	Joe Perches <joe@perches.com>,
	linux-s390@vger.kernel.org, kernel-janitors@vger.kernel.org,
	Harald Freudenberger <freude@linux.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Ingo Franzki <ifranzki@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: s390/pkey: Use memdup_user() rather than duplicating its implementation
Date: Thu, 7 Nov 2019 09:48:54 +0300	[thread overview]
Message-ID: <20191107064854.GM10409@kadam> (raw)
In-Reply-To: <a4eaf80e-a5dd-4da3-75ca-8231f01af193@de.ibm.com>

On Wed, Nov 06, 2019 at 07:30:19PM +0100, Christian Borntraeger wrote:
> 
> 
> 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.

Fixes tags are independent from backports.  If you want a backport you
should CC stable.

Fixes tags are useful for a bunch of things like when you're reviewing a
patch you can look at the original commit to see what was intended.
Also we can do automated analysis to see what sort of commits introduce
bugs (did they spend time in linux-next etc).

regards,
dan carpenter


WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Markus Elfring <Markus.Elfring@web.de>,
	Joe Perches <joe@perches.com>,
	linux-s390@vger.kernel.org, kernel-janitors@vger.kernel.org,
	Harald Freudenberger <freude@linux.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Ingo Franzki <ifranzki@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: s390/pkey: Use memdup_user() rather than duplicating its implementation
Date: Thu, 07 Nov 2019 06:48:54 +0000	[thread overview]
Message-ID: <20191107064854.GM10409@kadam> (raw)
In-Reply-To: <a4eaf80e-a5dd-4da3-75ca-8231f01af193@de.ibm.com>

On Wed, Nov 06, 2019 at 07:30:19PM +0100, Christian Borntraeger wrote:
> 
> 
> 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.

Fixes tags are independent from backports.  If you want a backport you
should CC stable.

Fixes tags are useful for a bunch of things like when you're reviewing a
patch you can look at the original commit to see what was intended.
Also we can do automated analysis to see what sort of commits introduce
bugs (did they spend time in linux-next etc).

regards,
dan carpenter

  reply	other threads:[~2019-11-07  6:50 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 10:22 [PATCH] s390/pkey: Use memdup_user() rather than duplicating its implementation Markus Elfring
2019-11-06 10:22 ` Markus Elfring
2019-11-06 10:38 ` Joe Perches
2019-11-06 10:38   ` Joe Perches
2019-11-06 13:00   ` Markus Elfring
2019-11-06 13:00     ` Markus Elfring
2019-11-06 17:29     ` Joe Perches
2019-11-06 17:29       ` Joe Perches
2019-11-06 18:55       ` Markus Elfring
2019-11-06 18:55         ` Markus Elfring
2019-11-06 19:01         ` Joe Perches
2019-11-06 19:01           ` Joe Perches
2019-11-06 19:18           ` Markus Elfring
2019-11-06 19:18             ` Markus Elfring
2019-11-06 13:00   ` Markus Elfring
2019-11-06 13:00     ` Markus Elfring
2019-11-06 18:30     ` Christian Borntraeger
2019-11-06 18:30       ` Christian Borntraeger
2019-11-07  6:48       ` Dan Carpenter [this message]
2019-11-07  6:48         ` Dan Carpenter
2019-11-07  8:07         ` Christian Borntraeger
2019-11-07  8:07           ` Christian Borntraeger
2019-11-07 10:06   ` [PATCH v2] " Markus Elfring
2019-11-07 10:06     ` Markus Elfring
2019-11-07 12:44     ` Christian Borntraeger
2019-11-07 12:44       ` Christian Borntraeger
2019-11-07 13:45       ` Markus Elfring
2019-11-07 13:45         ` Markus Elfring
2019-11-07 13:54         ` Christian Borntraeger
2019-11-07 13:54           ` Christian Borntraeger
2019-11-07 14:27           ` Markus Elfring
2019-11-07 14:27             ` Markus Elfring
2019-11-08 11:32             ` Christian Borntraeger
2019-11-08 11:32               ` Christian Borntraeger
2019-11-08 17:14               ` [PATCH v3] " Markus Elfring
2019-11-08 17:14                 ` Markus Elfring
2019-11-11  7:54                 ` Christian Borntraeger
2019-11-11  7:54                   ` Christian Borntraeger
2019-11-11  8:11                   ` [v3] " Markus Elfring
2019-11-11  8:11                     ` Markus Elfring
2019-11-11  8:27                     ` Christian Borntraeger
2019-11-11  8:27                       ` Christian Borntraeger
2019-11-11  8:42                       ` Markus Elfring
2019-11-11  8:42                         ` Markus Elfring
2019-11-11  8:56                         ` Christian Borntraeger
2019-11-11  8:56                           ` Christian Borntraeger
2019-11-11  9:06                           ` Markus Elfring
2019-11-11  9:06                             ` Markus Elfring
2019-11-11  9:08                             ` Christian Borntraeger
2019-11-11  9:08                               ` Christian Borntraeger
2019-11-11  9:17                               ` Markus Elfring
2019-11-11  9:17                                 ` Markus Elfring
2019-11-11  9:18                                 ` Christian Borntraeger
2019-11-11  9:18                                   ` Christian Borntraeger
2019-11-11  9:26                                   ` Markus Elfring
2019-11-11  9:26                                     ` Markus Elfring
2019-11-11 14:45                   ` [PATCH v4] s390/pkey: Fix memory leak in error case by using memdup_user() rather than open coding Markus Elfring
2019-11-11 14:45                     ` Markus Elfring
2019-11-11 16:40                     ` Christian Borntraeger
2019-11-11 16:40                       ` [PATCH v4] s390/pkey: Fix memory leak in error case by using memdup_user() rather than open codi Christian Borntraeger
2019-11-13 17:09                       ` [v4] s390/pkey: Fix memory leak in error case by using memdup_user() rather than open coding Markus Elfring
2019-11-13 17:09                         ` Markus Elfring

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=20191107064854.GM10409@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=Markus.Elfring@web.de \
    --cc=borntraeger@de.ibm.com \
    --cc=freude@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=ifranzki@linux.ibm.com \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.