From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761605AbcINRFK (ORCPT ); Wed, 14 Sep 2016 13:05:10 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:40541 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753427AbcINRFI (ORCPT ); Wed, 14 Sep 2016 13:05:08 -0400 Date: Wed, 14 Sep 2016 19:04:52 +0200 From: Peter Zijlstra To: SF Markus Elfring Cc: x86@kernel.org, Alexander Shishkin , Arnaldo Carvalho de Melo , "H. Peter Anvin" , Ingo Molnar , Thomas Gleixner , LKML , kernel-janitors@vger.kernel.org, Julia Lawall Subject: Re: perf/x86: Use kmalloc_array() in merge_attr() Message-ID: <20160914170452.GD5016@twins.programming.kicks-ass.net> References: <20160905075149.GQ10153@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 14, 2016 at 06:40:32PM +0200, SF Markus Elfring wrote: > > Would you like to suggest any more constraints for this kind of > software refactoring? Yes, don't do it. If you're writing new code by all means, do whatever you feel, but don't go changing code just because checkpatch. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Date: Wed, 14 Sep 2016 17:04:52 +0000 Subject: Re: perf/x86: Use kmalloc_array() in merge_attr() Message-Id: <20160914170452.GD5016@twins.programming.kicks-ass.net> List-Id: References: <20160905075149.GQ10153@twins.programming.kicks-ass.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: SF Markus Elfring Cc: x86@kernel.org, Alexander Shishkin , Arnaldo Carvalho de Melo , "H. Peter Anvin" , Ingo Molnar , Thomas Gleixner , LKML , kernel-janitors@vger.kernel.org, Julia Lawall On Wed, Sep 14, 2016 at 06:40:32PM +0200, SF Markus Elfring wrote: > > Would you like to suggest any more constraints for this kind of > software refactoring? Yes, don't do it. If you're writing new code by all means, do whatever you feel, but don't go changing code just because checkpatch.