Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Sang-Hoon Choi <csh0052@gmail.com>
Cc: gongfan1@huawei.com, netdev@vger.kernel.org, lcy8047@gmail.com
Subject: Re: [PATCH net] hinic3: handle auxiliary device ID allocation failure
Date: Mon, 28 Sep 2026 23:30:10 +0000	[thread overview]
Message-ID: <179063821090.174580.17192072801797214528.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <179001656835.91284.3719235813225229273.idr-bug-81@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 22 Sep 2026 03:49:28 +0900 you wrote:
> hinic3_init_hwdev() stores the result of hinic3_adev_idx_alloc() in
> hwdev->dev_id without checking for an error. If ID allocation fails but
> the remaining initialization succeeds, hinic3_add_one_adev() uses the
> negative error code as the auxiliary device ID instead of a reserved ID.
> 
> Return the allocation error before initializing the hardware. Add an
> unwind label that clears pci_adapter->hwdev and frees the allocation
> without attempting to release an ID that was never allocated.
> 
> [...]

Here is the summary with links:
  - [net] hinic3: handle auxiliary device ID allocation failure
    https://git.kernel.org/netdev/net-next/c/087827628ad3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-28 23:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 18:49 [PATCH net] hinic3: handle auxiliary device ID allocation failure Sang-Hoon Choi
2026-09-23  8:05 ` Fan Gong
2026-09-28 23:30 ` patchwork-bot+netdevbpf [this message]

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=179063821090.174580.17192072801797214528.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=csh0052@gmail.com \
    --cc=gongfan1@huawei.com \
    --cc=lcy8047@gmail.com \
    --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: 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