From: Jakub Kicinski <kuba@kernel.org>
To: manushprajwal <manushprajwal555@gmail.com>
Cc: sgoutham@marvell.com, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] net: thunder_bgx: fix fwnode leak in bgx_init_of_phy()
Date: Thu, 27 Aug 2026 08:56:03 -0700 [thread overview]
Message-ID: <20260827085603.2d37835f@kernel.org> (raw)
In-Reply-To: <20260823111231.372-1-manushprajwal555@gmail.com>
On Sun, 23 Aug 2026 16:42:31 +0530 manushprajwal wrote:
> Subject: [PATCH 1/2] net: thunder_bgx: fix fwnode leak in bgx_init_of_phy()
We never saw patch 2/2, you need to repost it as standalone or send
both to netdev.
--
pw-bot: cr
next prev parent reply other threads:[~2026-08-27 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 11:12 [PATCH 1/2] net: thunder_bgx: fix fwnode leak in bgx_init_of_phy() manushprajwal
2026-08-23 17:15 ` Markus Elfring
2026-08-27 15:56 ` Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-27 18:38 Manush Prajwal
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=20260827085603.2d37835f@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=manushprajwal555@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgoutham@marvell.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.