All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Guenter Roeck <linux@roeck-us.net>
Cc: michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	kalesh-anakkur.purayil@broadcom.com
Subject: Re: [PATCH] bnxt_en: Fix call to hardware monitoring event handler
Date: Sat, 22 Aug 2026 20:00:25 +0000	[thread overview]
Message-ID: <178742882588.1812309.229528138073093887.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260821044512.663941-1-linux@roeck-us.net>

Hello:

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

On Thu, 20 Aug 2026 21:45:12 -0700 you wrote:
> The first parameter of hwmon_notify_event() is supposed to be the hardware
> monitoring device. The bnxt driver calls it with the platform device as
> first parameter instead. This API break results in undefined behavior and
> may result in a crash.
> 
> Pass the hardware monitoring device as parameter instead to fix the
> problem.
> 
> [...]

Here is the summary with links:
  - bnxt_en: Fix call to hardware monitoring event handler
    https://git.kernel.org/netdev/net/c/622d698df423

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-08-22 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21  4:45 [PATCH] bnxt_en: Fix call to hardware monitoring event handler Guenter Roeck
2026-08-21  5:11 ` Kalesh Anakkur Purayil
2026-08-21 14:19 ` Vadim Fedorenko
2026-08-22 20:00 ` 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=178742882588.1812309.229528138073093887.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=pavan.chebbi@broadcom.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 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.