DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Soumyadeep Hore <soumyadeep.hore@intel.com>
Cc: <aman.deep.singh@intel.com>, <dev@dpdk.org>, <shaiq.wani@intel.com>
Subject: Re: [PATCH v1 0/9] Update IAVF Base Driver
Date: Tue, 17 Sep 2024 15:24:40 +0100	[thread overview]
Message-ID: <ZumRKL4zIRieXaIa@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <ZuhAuMPF-6xknAHN@bricha3-mobl1.ger.corp.intel.com>

On Mon, Sep 16, 2024 at 03:29:12PM +0100, Bruce Richardson wrote:
> On Tue, Sep 10, 2024 at 10:12:15AM +0000, Soumyadeep Hore wrote:
> > Updated the IAVF Base driver with latest sharedcode patches.
> > 
> > Ahmed Zaki (2):
> >   common/iavf: define the maximum MSIX index
> >   common/iavf: add RSS CONFIG hash function
> > 
> > Jacob Keller (1):
> >   common/iavf: update the PTP enablement in virtchnl
> > 
> > Julian Grajkowski (1):
> >   common/iavf: add RefSync support
> > 
> > Jun Zhang (1):
> >   common/iavf: add GNSS support over VF
> > 
> > Lukasz Plachno (1):
> >   common/iavf: add commands for HQOS management
> > 
> > Mateusz Polchlopek (1):
> >   common/iavf: add flex descriptor fields enum
> > 
> > Piotr Gardocki (1):
> >   common/iavf: add SyncE support over VF
> > 
> > Sudheer Mogilappagari (1):
> >   common/iavf: introduce QGRP capabilities to replace ADQ caps
> > 
> >  drivers/common/iavf/iavf_register.h |   3 +-
> >  drivers/common/iavf/iavf_type.h     |   4 +
> >  drivers/common/iavf/virtchnl.h      | 505 ++++++++++++++++++++++++++++
> >  3 files changed, 511 insertions(+), 1 deletion(-)
> >
> Series-acked-by: Bruce Richardson <bruce.richardson@intel.com>
> 
> Like the "ice" driver base code update, this series is missing a README
> update to record the date of the last snapshot. Before I push this series,
> can you please send a patch to update the drivers/common/iavf/README file.
> NOTE - the file needs more than just a date change: for example, it references
> a non-existant base directory.
> 
> /Bruce
> 
Applied to dpdk-next-net-intel along with the README update.

Thanks,
/Bruce

      reply	other threads:[~2024-09-17 14:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10 10:12 Soumyadeep Hore
2024-09-10 10:12 ` [PATCH v1 1/9] common/iavf: update the PTP enablement in virtchnl Soumyadeep Hore
2024-09-10 10:12 ` [PATCH v1 2/9] common/iavf: add SyncE support over VF Soumyadeep Hore
2024-09-10 10:12 ` [PATCH v1 3/9] common/iavf: add GNSS " Soumyadeep Hore
2024-09-10 10:12 ` [PATCH v1 4/9] common/iavf: define the maximum MSIX index Soumyadeep Hore
2024-09-10 10:12 ` [PATCH v1 5/9] common/iavf: add commands for HQOS management Soumyadeep Hore
2024-09-10 10:12 ` [PATCH v1 6/9] common/iavf: add flex descriptor fields enum Soumyadeep Hore
2024-09-10 10:12 ` [PATCH v1 7/9] common/iavf: add RefSync support Soumyadeep Hore
2024-09-10 10:12 ` [PATCH v1 8/9] common/iavf: introduce QGRP capabilities to replace ADQ caps Soumyadeep Hore
2024-09-10 10:12 ` [PATCH v1 9/9] common/iavf: add RSS CONFIG hash function Soumyadeep Hore
2024-09-16 14:29 ` [PATCH v1 0/9] Update IAVF Base Driver Bruce Richardson
2024-09-17 14:24   ` Bruce Richardson [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=ZumRKL4zIRieXaIa@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=shaiq.wani@intel.com \
    --cc=soumyadeep.hore@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;
as well as URLs for NNTP newsgroup(s).