DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Brandes, Shai" <shaibran@amazon.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH 0/7] net/ena: release 2.13.0
Date: Wed, 2 Jul 2025 08:48:10 +0000	[thread overview]
Message-ID: <SN1PR18MB23514CFC26B657D25DBAFA3EAF40A@SN1PR18MB2351.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250630111358.3476-1-shaibran@amazon.com>

Recheck-request: aws-unit-testing
We added support for rerun to aws lab bot, this is to verify it function well on the cover letter option

> -----Original Message-----
> From: Brandes, Shai <shaibran@amazon.com>
> Sent: Monday, June 30, 2025 2:14 PM
> To: stephen@networkplumber.org
> Cc: dev@dpdk.org; Brandes, Shai <shaibran@amazon.com>
> Subject: [PATCH 0/7] net/ena: release 2.13.0
> 
> This patchset includes an upgrade of the ENA HAL, introduces a new feature,
> and addresses three bug fixes.
> 
> Thank you in advance to the net maintainers and community members for
> your time and effort reviewing the code.
> 
> Best regards,
> Shai Brandes
> AWS Elastic Network Adapter team
> 
> ---
> v2:
> Removed patch "net/ena: fix virtual address calc for unaligned BARs"
> which contained a problematic casting when compiling with 32-bit system
> 
> v3:
> no change, there was some technical issue when sending the emails where
> part of the patches apeared on different series.
> 
> v4:
> Each patch in the series should compile independently.
> Patch 4/7 causes a compile error that was missed, as the full series passed our
> directed tests when applied together
> 
> v5:
> Reworked the patchset so it applies cleanly on origin/main due to release
> notes mismatch.
> 
> Shai Brandes (7):
>   net/ena/base: avoid recalculating desc per entry
>   net/ena/base: coding style changes
>   net/ena: separate doorbell logic for Rx and Tx
>   net/ena: support fragment bypass mode
>   net/ena: fix unhandled interrupt config failure
>   net/ena: fix aenq timeout with low poll interval
>   net/ena: upgrade driver version to 2.13.0
> 
>  doc/guides/nics/ena.rst                       | 13 ++-
>  doc/guides/rel_notes/release_25_07.rst        |  9 ++
>  drivers/net/ena/base/ena_com.c                | 40 +++++++-
>  drivers/net/ena/base/ena_com.h                |  7 ++
>  .../net/ena/base/ena_defs/ena_admin_defs.h    | 14 +++
>  drivers/net/ena/base/ena_eth_com.c            |  6 +-
>  drivers/net/ena/base/ena_eth_com.h            | 15 ++-
>  drivers/net/ena/ena_ethdev.c                  | 98 +++++++++++++++----
>  drivers/net/ena/ena_ethdev.h                  |  4 +-
>  9 files changed, 175 insertions(+), 31 deletions(-)
> 
> --
> 2.17.1


      parent reply	other threads:[~2025-07-02  8:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30 11:13 Shai Brandes
2025-06-30 11:13 ` [PATCH 1/7] net/ena/base: avoid recalculating desc per entry Shai Brandes
2025-06-30 11:13 ` [PATCH 2/7] net/ena/base: coding style changes Shai Brandes
2025-06-30 11:13 ` [PATCH 3/7] net/ena: separate doorbell logic for Rx and Tx Shai Brandes
2025-06-30 11:13 ` [PATCH 4/7] net/ena: support fragment bypass mode Shai Brandes
2025-06-30 11:22 ` [PATCH 0/7] net/ena: release 2.13.0 Brandes, Shai
2025-06-30 18:43 ` Stephen Hemminger
2025-07-02  8:48 ` Brandes, Shai [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=SN1PR18MB23514CFC26B657D25DBAFA3EAF40A@SN1PR18MB2351.namprd18.prod.outlook.com \
    --to=shaibran@amazon.com \
    --cc=dev@dpdk.org \
    /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).