Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755189AbcJSOL1 (ORCPT ); Wed, 19 Oct 2016 10:11:27 -0400 Received: from mout.web.de ([212.227.15.14]:61550 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752030AbcJSOLR (ORCPT ); Wed, 19 Oct 2016 10:11:17 -0400 Subject: Re: [media] winbond-cir: Move a variable assignment in wbcir_tx() To: =?UTF-8?Q?David_H=c3=a4rdeman?= , linux-media@vger.kernel.org References: <1a68a0e8-6d56-d9c1-058b-cf9cd8122acb@users.sourceforge.net> <26ee4adb-2637-52c3-ac83-ae121bed5eff@users.sourceforge.net> <566ABCD9.1060404@users.sourceforge.net> <1d7d6a2c-0f1e-3434-9023-9eab25bb913f@users.sourceforge.net> <78ddb54d61d871ad4b81c986dd9a32d4@hardeman.nu> Cc: Mauro Carvalho Chehab , Sean Young , LKML , kernel-janitors@vger.kernel.org, Julia Lawall From: SF Markus Elfring Message-ID: <71669997-fda1-6b97-9599-4b8118a20fb7@users.sourceforge.net> Date: Wed, 19 Oct 2016 16:05:59 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:Fv/nJmjB/XpMxrmbfQokyFqOGYxNzaLl4TYgECtJD0SHnBrrpTx wVPXcNCZDHAJXv7yYNoGTi4jY1KmEbX2I0cz07CFvi1gmxe53MWQqWX7g4Dp3I9qQarmsys UBvEZiAj5JF00L6D5X7zmKuE1y9too9vt7A4B0OLqdjpuh3Ffx3DsVzbPPwmUSJmCCzApvW Peo5dhxD0Hti0DkkzRn+Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:BBa6ZdhHL9A=:efhzBvSAP9HGldWAnCWc8m /CSSMFAzkBg5o/81LcUKrWMqTQegYm4fmC7sq4SaELXeGiLEtNIirC0hjtTt6011Yh4HaJBUf HKtxvAFYcwrvX8PKMpSet7EXblA6Oth6com5ywL6KApRenDbyoYYuMTPLiBCYVPsfwFSGMfmT Ok9V4IMSzYYaEUxMsFnEnmvBLJepc7NnO5xn8mnvve8MHNR5N1lZ4Bu8M40sBTR8kynpPSOnn X46t6T4AFcdKM1ub+qTHkXkC15AbBERUlwRfa+dipMVGXKIVB6Bb1WMh3gDl7y34yITScd7K1 uJQtLdtZVXGe7sIb6JfeYxnenlZ+d2T4vFHrOA+9gdcTfcf41POeKTbebXh4ZJjQuf0I68Ogy 7Ayg8wP5kqjeFBMXGahhVUBk/Qe997UtGzopikBiNmjDihzN17QJIxgK2pgYqnveXolRS5oDc 2uahSnPayJvDRD0Tvi3McqUZpRmWLADNgsHHMnZkSuU7ekxrW7lcrLVKk/TCrjXluclrRTSb5 GAQBOWnn7tvsBOjz9FRQUWENBy4PMiMuGwN3gMYmEWbdbMknU7S0Nf+EqsXosgwE97EkprjnE Xy+ZwiNuJfsFWtjhfZ4uc50jok7SB88jPbHK7Hav4OgTY2jBy7DXOLQcZ2ZJgWihElz5bhxpp yAd5049icy0N7DANolCd/2o2podWwZmsIkvejb+OVgcmUI9/QBpFgAvQCF1c0/PVXMhrOF69l YuPRIAejlReQLWRDaTsfAV1FDFh1O2m4xS1v2LRmcZSq0Jza6anvK6UGIAuuaz47abycD1vAz mejKD5s Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 532 Lines: 18 >> * How do you think about to avoid a variable assignment in case >> that this memory allocation failed anyhow? > > There is no memory allocation that can fail at this point. Do you really know the failure probability for a call of the function "kmalloc" (within the function "wbcir_tx") under all possible run time situations? >> * Do you care for data access locality? > > Not unless you can show measurable performance improvements? Did any software developer (before me) dare anything in this direction? Regards, Markus