Netdev List
 help / color / mirror / Atom feed
From: Ratheesh Kannoth <rkannoth@marvell.com>
To: 최유호 <dbgh9129@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
	Sunil Goutham <sgoutham@marvell.com>,
	Linu Cherian <lcherian@marvell.com>,
	Geetha sowjanya <gakula@marvell.com>,
	hariprasad <hkelam@marvell.com>,
	Subbaraya Sundeep <sbhatta@marvell.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <nshettyj@marvell.com>
Subject: Re: [PATCH net-next v2] octeontx2-af: Fix PCI device reference leaks in debugfs
Date: Fri, 12 Jun 2026 07:28:36 +0530	[thread overview]
Message-ID: <aitnzFHczBlsY_O0@rkannoth-OptiPlex-7090> (raw)
In-Reply-To: <CACrCO_UAjAdi3K7y0nHcSDoCXaZnZRCZ46b3u3vdfyWEY1GC9w@mail.gmail.com>

On 2026-06-12 at 00:33:50, 최유호 (dbgh9129@gmail.com) wrote:
> > Oh, that's much better, somehow I assumed that this dance is necessary
> > because we are accessing a different PCI device.
> >
> > Also, since you're actively working upstream and nobody else on the CC
> > list responded - should you perhaps be added to maintainers for this
> > driver so that you're CCed on patches?  (instead of one of the useless
> > ones)
>
> Thank you for reviewing this patch.
>
> If Marvell posts a cleanup patch for this issue, could you please include:
> Reported-by: Yuho Choi dbgh9129@gmail.com
> or otherwise mention this report?
> I will hold off on sending another revision for now.

Thank you for catching this issue and for posting the fix!

We currently have a large backlog of patches queued up to post upstream, so
there will likely be a bit of a delay if we handle the submission from our
side. If you have the bandwidth and would like to post this (passing rvu object to debugfs file)
yourself, please feel free—we will gladly help review and test it promptly.

Alternatively, if you prefer that Marvell takes it over and posts the
cleanup, we will definitely include your tag to ensure proper credit.

  reply	other threads:[~2026-06-12  1:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 16:55 [PATCH net-next v2] octeontx2-af: Fix PCI device reference leaks in debugfs Yuho Choi
2026-06-10 15:35 ` Jakub Kicinski
2026-06-11  2:21   ` Ratheesh Kannoth
2026-06-11 17:45     ` Jakub Kicinski
2026-06-11 19:03       ` 최유호
2026-06-12  1:58         ` Ratheesh Kannoth [this message]
2026-06-12 15:35           ` 최유호
2026-06-12  1:49       ` Ratheesh Kannoth

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=aitnzFHczBlsY_O0@rkannoth-OptiPlex-7090 \
    --to=rkannoth@marvell.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dbgh9129@gmail.com \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=hkelam@marvell.com \
    --cc=kuba@kernel.org \
    --cc=lcherian@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nshettyj@marvell.com \
    --cc=pabeni@redhat.com \
    --cc=sbhatta@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox