From: Thomas Monjalon <thomas@monjalon.net>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: ci@dpdk.org, Ali Alnubani <alialnu@nvidia.com>,
Patrick Robb <probb@iol.unh.edu>
Subject: Re: BNXT patches
Date: Thu, 23 Oct 2025 01:36:03 +0200 [thread overview]
Message-ID: <6873353.2l3rmUXbR5@thomas> (raw)
In-Reply-To: <CAJvnSUAw9U78GhsBdU4XmiFTM+QA1i6EpNnt=3Zv7d_SvD_u1Q@mail.gmail.com>
Hello,
Not related to CI, but the best would be to not wait a year
for updating the driver in one series.
As you maintain a repository branch,
you can merge the patches and wait for UNH CI running on it.
Also the GitHub robot can run if you push in a GitHub repo.
23/10/2025 01:05, Patrick Robb:
> Hi Ajit,
>
> That sounds annoying. A sanity check question to start - is there any sense
> in resubmitting the series and just intentionally delaying sending the 2nd
> half of the commits? I.e.
>
> 1. git send-email /my-patches-dir/*
> 2. Send the first 30
> 3. At prompt for 31st patch, pause.
> 4. wait 10 minutes.
> 5. Return to terminal, send patches 31 through 57.
>
> Or, if this is not possible, I think there should be some solution on the
> patchwork mail server policy side. I think Ali Alnubani from NVIDIA manages
> it and he is usually pretty responsive with such modification requests. We
> could ask about solutions like:
>
> 1. Add a complete exception to the mail server message rate restriction for
> emails coming from email addresses associated with DPDK member companies.
>
> or
>
> 2. Simply make the message rate restrictions more permissive than they are
> currently (i.e. allow 100 emails, not 30).
>
> If the ideas above will not work, I will have to assess the "bundle" idea
> tomorrow when I have time available than I do right now. Most likely it's
> technically possible to facilitate but I do feel like simply resolving the
> original issue (the mail server is not letting you submit your series) and
> allowing the CI system automation to intake the patchseries from patchwork
> in the normal way is the ideal approach.
>
> On Wed, Oct 22, 2025 at 5:39 PM Ajit Khaparde <ajit.khaparde@broadcom.com>
> wrote:
>
> > Hi Patrick,
> > When Manish was submitting his patchset,
> > Looks like because of a mail server message rate restriction,
> > only 31 of 57 patches went through in the first attempt
> >
> > He submitted the remaining patches 32 to 57 in second attempt.
> >
> > I created a bundle for the series now. [1]
> >
> > Also a couple of patches were stuck at the gate.
> > So a proper build has not happened on the patchset yet. [2]
> > Do we have a way to trigger a build on the bundle?
> >
> > Please advise.
> >
> > [1] https://patchwork.dpdk.org/bundle/ajitkhaparde/BNXT%2025.11/
> > [2] https://mails.dpdk.org/archives/test-report/2025-October/921500.html
> >
> > Thanks
> > Ajit
next prev parent reply other threads:[~2025-10-22 23:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACZ4nhvBbK1kC8oCwkHRn+Mnov9zXgAwUsKduEc8wO3EXs7huw@mail.gmail.com>
2025-10-22 23:05 ` Patrick Robb
2025-10-22 23:36 ` Thomas Monjalon [this message]
2025-10-22 23:52 ` Patrick Robb
2025-10-23 0:09 ` Ajit Khaparde
2025-10-23 0:36 ` Patrick Robb
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=6873353.2l3rmUXbR5@thomas \
--to=thomas@monjalon.net \
--cc=ajit.khaparde@broadcom.com \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.org \
--cc=probb@iol.unh.edu \
/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).