DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Brandes, Shai" <shaibran@amazon.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v4 0/7] net/ena: release 2.13.0
Date: Mon, 30 Jun 2025 07:54:34 -0700	[thread overview]
Message-ID: <20250630075434.02a990e6@hermes.local> (raw)
In-Reply-To: <6be9d6041a3e4cdea8ed6609c32f9b38@amazon.com>

On Mon, 30 Jun 2025 11:08:12 +0000
"Brandes, Shai" <shaibran@amazon.com> wrote:

> > -----Original Message-----
> > From: Stephen Hemminger <stephen@networkplumber.org>
> > Sent: Sunday, June 29, 2025 7:50 PM
> > To: Brandes, Shai <shaibran@amazon.com>
> > Cc: dev@dpdk.org
> > Subject: RE: [EXTERNAL] [PATCH v4 0/7] net/ena: release 2.13.0
> > 
> > CAUTION: This email originated from outside of the organization. Do not click
> > links or open attachments unless you can confirm the sender and know the
> > content is safe.
> > 
> > 
> > 
> > On Wed, 28 May 2025 13:25:24 +0300
> > Shai Brandes <shaibran@amazon.com> wrote:
> >   
> > > 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  
> > 
> > Could you check against current main branch.
> > This no longer applies, either it already got merged or something changed.  
> Hi Stephen, the merge conflict occurred due to updates in the release notes after we initially uploaded the patchset.
> I've rebased the changes on top of origin/main and will submit a revised version shortly. I'll go ahead and abandon the previous set.
> 
> Just a quick note, we originally submitted the patchset over a month ago, and it has been in the "awaiting upstream" state since then.
> I noticed that rc2 has already been released.
> we would greatly appreciate it if you could include the ENA changes in rc3.
> ENA is a self-contained module, and the previous maintainer approved that mode of operation. Hopefully, an exception can be made in this case.
> Thanks again for your time and continued support. 

Thanks, that version got lost in the huge patchsets that were sitting in backlog.

      reply	other threads:[~2025-06-30 14:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28 10:25 Shai Brandes
2025-05-28 10:25 ` [PATCH v4 1/7] net/ena/base: avoid recalculating desc per entry Shai Brandes
2025-05-28 10:25 ` [PATCH v4 2/7] net/ena/base: coding style changes Shai Brandes
2025-05-28 10:25 ` [PATCH v4 3/7] net/ena: separate doorbell logic for Rx and Tx Shai Brandes
2025-05-28 10:25 ` [PATCH v4 4/7] net/ena: support fragment bypass mode Shai Brandes
2025-06-29 16:49 ` [PATCH v4 0/7] net/ena: release 2.13.0 Stephen Hemminger
2025-06-30 11:08   ` Brandes, Shai
2025-06-30 14:54     ` Stephen Hemminger [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=20250630075434.02a990e6@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=shaibran@amazon.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).