From: Manuel Ebner <manuelebner@mailbox.org>
To: Markus Elfring <Markus.Elfring@web.de>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Shiraz Saleem <shiraz.saleem@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH net-next] i40e: Use common error handling code in i40e_register_auxiliary_dev()
Date: Wed, 10 Jun 2026 10:30:59 +0200 [thread overview]
Message-ID: <c80c7ad9aa48dca8799ed2e76b1628aa7bec92b0.camel@mailbox.org> (raw)
In-Reply-To: <f0b4e354-9ed7-43f5-8ffe-97019e421c02@web.de>
On Wed, 2026-06-10 at 10:20 +0200, Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Wed, 10 Jun 2026 10:02:58 +0200
>
> [...]
>
> diff --git a/drivers/net/ethernet/intel/i40e/i40e_client.c
> b/drivers/net/ethernet/intel/i40e/i40e_client.c
> index 84a97ca8a6d8..389b8b83afbd 100644
> --- a/drivers/net/ethernet/intel/i40e/i40e_client.c
> +++ b/drivers/net/ethernet/intel/i40e/i40e_client.c
> @@ -304,15 +304,15 @@ static int i40e_register_auxiliary_dev(struct i40e_info *ldev,
> const char *name)
> ldev->aux_dev = aux_dev;
>
> ret = ida_alloc(&i40e_client_ida, GFP_KERNEL);
> - if (ret < 0) {
> - kfree(i40e_aux_dev);
> - return ret;
> - }
> + if (ret < 0)
> + goto free_aux_dev;
> +
> aux_dev->id = ret;
>
> ret = auxiliary_device_init(aux_dev);
> if (ret < 0) {
> ida_free(&i40e_client_ida, aux_dev->id);
> +free_aux_dev:
> kfree(i40e_aux_dev);
> return ret;
why do you do this? There's no functional change, right?
is it just readability?
Thanks
Manuel
next prev parent reply other threads:[~2026-06-10 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 8:20 Markus Elfring
2026-06-10 8:30 ` Manuel Ebner [this message]
2026-06-10 10:36 ` Markus Elfring
2026-06-10 9:12 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-06-11 9:13 ` Jagielski, Jedrzej
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=c80c7ad9aa48dca8799ed2e76b1628aa7bec92b0.camel@mailbox.org \
--to=manuelebner@mailbox.org \
--cc=Markus.Elfring@web.de \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=shiraz.saleem@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®