From: Stephen Hemminger <stephen@networkplumber.org>
To: "Brandes, Shai" <shaibran@amazon.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v3 0/7] net/ena: release 2.13.0
Date: Mon, 26 May 2025 07:44:18 -0700 [thread overview]
Message-ID: <20250526074418.2241b32e@hermes.local> (raw)
In-Reply-To: <2dfaa5f5cb1a44d8bbb001d19b72211e@amazon.com>
On Mon, 26 May 2025 14:13:27 +0000
"Brandes, Shai" <shaibran@amazon.com> wrote:
> Hi Stephen, and apologies for the multiple patchsets.
>
> We had a bug in our CI that prevented failed runs from showing up correctly in the report, this has just been identified and fixed.
> While rechecking, we discovered that one of the patches in the latest v3 patchset is currently failing to compile. The problematic line was replaced in a later patch within the same set, so when applied as a whole, the series passed in our directed tests.
>
> Problematic patch: [v3,4/7] net/ena: support fragment bypass mode https://patches.dpdk.org/project/dpdk/patch/20250522132614.3379-5-shaibran@amazon.com
> Failure on the entire patchset is now visible under https://patches.dpdk.org/project/dpdk/patch/20250522133029.3575-1-shaibran@amazon.com/
>
> Since we aim for each patch to compile independently, we'll need to abandon this patchset.
> Could you please advise whether you'd prefer to abandon it yourself, since it's already marked as *Awaiting Upstream* and it appear on the remote "for-main" branch, or should we just change the state to *Superseded*?
> Thanks again for your time and help!
>
> Shai
No worries, was relatively easy to update to the correct version.
Yeah, mark the latest correct version as Awaiting Upstream, and other should be Superseded.
next prev parent reply other threads:[~2025-05-26 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 14:13 [PATCH v3 0/7] net/ena: release 2.13.0 Brandes, Shai
2025-05-26 14:44 ` Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-22 13:26 Shai Brandes
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=20250526074418.2241b32e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.