From: Jakub Kicinski <kuba@kernel.org> To: Christophe JAILLET <christophe.jaillet@wanadoo.fr> Cc: davem@davemloft.net, fthain@telegraphics.com.au, 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 Date: Sat, 9 May 2020 11:13:21 -0700 [thread overview] Message-ID: <20200509111321.51419b19@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw) In-Reply-To: <50ef36cd-d095-9abe-26ea-d363d11ce521@wanadoo.fr> On Sat, 9 May 2020 18:47:08 +0200 Christophe JAILLET wrote: > Le 09/05/2020 à 03:54, Jakub Kicinski a écrit : > > 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. > > Right. > > The reason of this clean-up is that I wanted to avoid a checkpatch > warning with the proposed patch and I felt that having the same layout > in the error handling path of the probe function and in the remove > function was clearer. > So I updated also the remove function. I understand the motivation is good. > Fell free to ignore this hunk if not desired. I will not sent a V2 only > for that. That's not how it works. Busy maintainers don't have time to hand edit patches. I'm not applying this to the networking tree and I'm tossing it from patchwork. Please address the basic feedback. Thank you.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org> To: Christophe JAILLET <christophe.jaillet@wanadoo.fr> Cc: davem@davemloft.net, fthain@telegraphics.com.au, 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 Date: Sat, 09 May 2020 18:13:21 +0000 [thread overview] Message-ID: <20200509111321.51419b19@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw) In-Reply-To: <50ef36cd-d095-9abe-26ea-d363d11ce521@wanadoo.fr> On Sat, 9 May 2020 18:47:08 +0200 Christophe JAILLET wrote: > Le 09/05/2020 à 03:54, Jakub Kicinski a écrit : > > 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. > > Right. > > The reason of this clean-up is that I wanted to avoid a checkpatch > warning with the proposed patch and I felt that having the same layout > in the error handling path of the probe function and in the remove > function was clearer. > So I updated also the remove function. I understand the motivation is good. > Fell free to ignore this hunk if not desired. I will not sent a V2 only > for that. That's not how it works. Busy maintainers don't have time to hand edit patches. I'm not applying this to the networking tree and I'm tossing it from patchwork. Please address the basic feedback. Thank you.
next prev parent reply other threads:[~2020-05-09 18:13 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-08 17:25 [PATCH] net/sonic: Fix some resource leaks in error handling paths Christophe JAILLET 2020-05-08 17:25 ` Christophe JAILLET 2020-05-08 23:28 ` Finn Thain 2020-05-08 23:28 ` Finn Thain 2020-05-09 0:57 ` Jakub Kicinski 2020-05-09 0:57 ` Jakub Kicinski 2020-05-09 1:57 ` Finn Thain 2020-05-09 1:57 ` Finn Thain 2020-05-09 2:04 ` Jakub Kicinski 2020-05-09 2:04 ` Jakub Kicinski 2020-05-09 1:54 ` Jakub Kicinski 2020-05-09 1:54 ` Jakub Kicinski 2020-05-09 16:47 ` Christophe JAILLET 2020-05-09 16:47 ` Christophe JAILLET 2020-05-09 18:13 ` Jakub Kicinski [this message] 2020-05-09 18:13 ` Jakub Kicinski 2020-05-09 20:31 ` Christophe JAILLET 2020-05-09 20:31 ` Christophe JAILLET 2020-05-09 22:42 ` Joe Perches 2020-05-09 22:42 ` Joe Perches 2020-05-09 23:32 ` David Miller 2020-05-09 23:32 ` David Miller 2020-05-09 23:41 ` Joe Perches 2020-05-09 23:41 ` Joe Perches 2020-05-09 23:52 ` Finn Thain 2020-05-09 23:52 ` Finn Thain 2020-05-09 6:15 Markus Elfring 2020-05-09 6:15 ` Markus Elfring 2020-05-09 23:45 ` Finn Thain 2020-05-09 23:45 ` Finn Thain 2020-05-10 5:30 ` Markus Elfring 2020-05-10 5:30 ` Markus Elfring 2020-05-10 8:25 ` Finn Thain 2020-05-10 8:25 ` Finn Thain 2020-05-10 9:07 ` Markus Elfring 2020-05-10 9:07 ` Markus Elfring 2020-05-11 0:28 ` Finn Thain 2020-05-11 0:28 ` Finn Thain 2020-05-11 6:48 ` Markus Elfring 2020-05-11 6:48 ` Markus Elfring 2020-05-12 0:08 ` Finn Thain 2020-05-12 0:08 ` Finn Thain 2020-05-12 6:38 ` Markus Elfring 2020-05-12 6:38 ` Markus Elfring 2020-05-13 1:14 ` Finn Thain 2020-05-13 1:14 ` Finn Thain 2020-05-13 5:07 ` net/sonic: Software evolution around the application of coding standards Markus Elfring 2020-05-13 5:07 ` Markus Elfring 2020-05-13 23:16 ` Finn Thain 2020-05-13 23:16 ` Finn Thain 2020-05-11 8:20 ` net/sonic: Fix some resource leaks in error handling paths Markus Elfring 2020-05-11 8:20 ` 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=20200509111321.51419b19@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \ --to=kuba@kernel.org \ --cc=christophe.jaillet@wanadoo.fr \ --cc=davem@davemloft.net \ --cc=fthain@telegraphics.com.au \ --cc=kernel-janitors@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=netdev@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: linkBe 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.