Netdev List
 help / color / mirror / Atom feed
From: Satish Kharat <satishkh@cisco.com>
To: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>
Cc: Satish Kharat <satishkh@cisco.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sesidhar Baddela <sebaddel@cisco.com>,
	Aravind Dhanasekaran <aradhana@cisco.com>,
	Reese Faucette <rfaucett@cisco.com>
Subject: Re: [PATCH net 0/3] enic: fence DMA ownership and identify V2 VFs
Date: Tue, 20 Oct 2026 17:30:58 -0700	[thread overview]
Message-ID: <20261021003058.2214487-1-satishkh@cisco.com> (raw)
In-Reply-To: <20261016-b4-enic-dma-vf-index-net-generic-first-v1-20261010-v1-0-d27b55f69883@cisco.com>

Thanks for the review.

I have been investigating these findings and am preparing v2.

The revision will focus on the admin-channel DMA lifetime and VF mailbox
source fixes. I will drop the generic datapath quarantine changes from
this series and address that work separately, including the page-pool
lifetime concerns.

I will explain the disposition of the findings with the revision.

Thanks,
Satish

pw-bot: changes-requested

      parent reply	other threads:[~2026-10-21  0:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16  7:57 [PATCH net 0/3] enic: fence DMA ownership and identify V2 VFs Satish Kharat
2026-10-16  7:57 ` [PATCH net 1/3] enic: retain datapath DMA resources until queues stop Satish Kharat
2026-10-16  7:57 ` [PATCH net 2/3] enic: retain admin-channel DMA " Satish Kharat
2026-10-16  7:57 ` [PATCH net 3/3] enic: require DEVCMD2 and set the V2 VF mailbox source Satish Kharat
2026-10-21  0:30 ` Satish Kharat [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=20261021003058.2214487-1-satishkh@cisco.com \
    --to=satishkh@cisco.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=aradhana@cisco.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rfaucett@cisco.com \
    --cc=sebaddel@cisco.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