Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp727334ybk; Sat, 9 May 2020 16:54:03 -0700 (PDT) X-Google-Smtp-Source: APiQypIQ7u9FFFpr7LqC3rWWdaO8xMKxotbIDZ66B+FLY/cAV7rxrF6hxQwmCD4WMjAGpKAymy1/ X-Received: by 2002:a05:6402:154e:: with SMTP id p14mr7492731edx.326.1589068443591; Sat, 09 May 2020 16:54:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589068443; cv=none; d=google.com; s=arc-20160816; b=CgT8gGAUmgZYlGs5bA1q1H5BniE6OmkiRouRuVI+IarU0kyq7iLoaKWT/+xIqHlDUm 3C2CJjx3hYGI+guvVYhGDUjOWGqP++l2XIpdfEy/VGK5y6v0wlxkvm0yr3s32CjAn95r BaMaci9hgcQJpnk+pjNn8u7PyUzc9d1cw0bfn0MoEArjZSV1xJaL/83cPDiC6ScPaoJD 8omI9AzdOwi4L2bcBmnvqQduGPoc9WCd5e11ariVeG71D+aUKPi2t2G5ZvFN/rR97nq/ E1vdzx8d0ws+FQchQUoHpUmIccJnIzqzn9IPUUft4eDm2K9z1TLdjF0zNq6XdXf2hK79 Fk+Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:message-id :in-reply-to:subject:cc:to:from:date; bh=fJFrI7VrWYpd+WuX3cNErF+5IX++pBO3FeKez6YXgLI=; b=Ip8HgRkeHYN8+lGZlxKXYRcruH1h7KOTwbL+zCAd5I0B2BxQsbZlZv4S3DqZCa08Hu n7fU1CpZhuQcRK0b0wmRzP5I8n+VPXx+DXSFS+MZm00AldZvQIS+a6AZqvlAd4j+vy9k 3p85TkxeYYOz92xDLpPijJHw2asAxGWV64eGGfrj8JWsvefrrvmrI9H9X1hcug96TvXp Ejh39VoHGeFThD6BBjon7lLFCmmTpRKXOuoc4QTdEwyY23yPvmwBsoz65urpAtCT+tlK ehmOeVQIkwPMoGHiJUXx8MdaNj7as30efFk31E5HbZiJTPV873r1Rs7TUJkJVprX6tSR RwsA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g2si318558edq.421.2020.05.09.16.53.40; Sat, 09 May 2020 16:54:03 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727067AbgEIXwW (ORCPT + 99 others); Sat, 9 May 2020 19:52:22 -0400 Received: from kvm5.telegraphics.com.au ([98.124.60.144]:36590 "EHLO kvm5.telegraphics.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726026AbgEIXwV (ORCPT ); Sat, 9 May 2020 19:52:21 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by kvm5.telegraphics.com.au (Postfix) with ESMTP id 36E062996C; Sat, 9 May 2020 19:52:17 -0400 (EDT) Date: Sun, 10 May 2020 09:52:24 +1000 (AEST) From: Finn Thain To: Jakub Kicinski cc: Christophe JAILLET , davem@davemloft.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org Subject: Re: [PATCH] net/sonic: Fix some resource leaks in error handling paths In-Reply-To: <20200508185402.41d9d068@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> Message-ID: References: <20200508172557.218132-1-christophe.jaillet@wanadoo.fr> <20200508185402.41d9d068@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 8 May 2020, Jakub Kicinski wrote: > On Fri, 8 May 2020 19:25:57 +0200 Christophe JAILLET wrote: > > @@ -527,8 +531,9 @@ static int mac_sonic_platform_remove(struct platform_device *pdev) > > struct sonic_local* lp = netdev_priv(dev); > > > > unregister_netdev(dev); > > - dma_free_coherent(lp->device, SIZEOF_SONIC_DESC * SONIC_BUS_SCALE(lp->dma_bitmode), > > - lp->descriptors, lp->descriptors_laddr); > > + dma_free_coherent(lp->device, > > + SIZEOF_SONIC_DESC * SONIC_BUS_SCALE(lp->dma_bitmode), > > + lp->descriptors, lp->descriptors_laddr); > > free_netdev(dev); > > > > return 0; > > This is a white-space only change, right? Since this is a fix we should > avoid making cleanups which are not strictly necessary. > I think it is harmless if it doesn't create any merge conflicts. Any merge conflict created by the whitespace change would have happened anyway, because all of the changes in this patch are very closely related. That's why I was happy to put a 'reviewed-by' tag on this.