mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Alexander Lobakin <aleksander.lobakin@intel.com>,
	Pavan Kumar Linga <pavan.kumar.linga@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	<intel-wired-lan@lists.osuosl.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v7 00/15] Introduce Intel IDPF driver
Date: Tue, 13 Jun 2023 09:23:19 -0700	[thread overview]
Message-ID: <d9fd12f1-a858-c67e-b17f-2299bba9b17c@intel.com> (raw)
In-Reply-To: <293a81d3-f0b4-904c-a5f9-64ce091f1ecd@intel.com>

On 6/13/2023 4:47 AM, Alexander Lobakin wrote:
> From: Pavan Kumar Linga <pavan.kumar.linga@intel.com>
> Date: Mon, 12 Jun 2023 16:10:06 -0700
> 
>> This patch series introduces the Intel(R) Infrastructure Data Path Function
>> (IDPF) driver. It is used for both physical and virtual functions. Except
> 
> No netdev maintainers and generic MLs, not speaking that the previous
> versions already were there? What?

This was something I told Pavan he could do as this likely will be 
turned around as the v2 PR. I was trying to save some extra thrash of, 
nearly identical, iwl-next v7 and net-next v2 being sent in a short 
timespan.

Thanks,
Tony

      reply	other threads:[~2023-06-13 16:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230612231021.39409-1-pavan.kumar.linga@intel.com>
2023-06-13 11:47 ` Alexander Lobakin
2023-06-13 16:23   ` Tony Nguyen [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=d9fd12f1-a858-c67e-b17f-2299bba9b17c@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pavan.kumar.linga@intel.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
all inboxes | Powered by JetHome®