DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Aaron Conole" <aconole@redhat.com>
Cc: <dev@dpdk.org>
Subject: RE: Depends-on
Date: Wed, 29 May 2024 16:40:00 +0200	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F4CE@smartserver.smartshare.dk> (raw)
In-Reply-To: <f7tmso8lmbg.fsf@redhat.com>

> From: Aaron Conole [mailto:aconole@redhat.com]
> Sent: Wednesday, 29 May 2024 16.34
> 
> Morten Brørup <mb@smartsharesystems.com> writes:
> 
> > Aaron,
> >
> > I have been trying to submit a patch with a dependency on another
> > patch, but it keeps failing, and the error message "Apply patch set
> > 140352 failed: 404 Not Found" isn't very helpful.
> >
> > Could you please take a look at it and let me know what's going on:
> > https://patchwork.dpdk.org/project/dpdk/patch/20240528070546.92511-1-
> mb@smartsharesystems.com/
> 
> Sure - I'll take a look.

Thank you.

> 
> From the github robot side, it looks like we currently only support
> dependencies via a series- request.

Oh, I didn't notice.

A previous version of the patch depended on the series, and passed github, but failed at IOL and Intel (like this version did):
https://patchwork.dpdk.org/project/dpdk/patch/20240527131659.80164-1-mb@smartsharesystems.com/

> 
> I'll try to spend some time and add patch based support, but I think
> there was some weird tricky stuff going on.

Series support suffices for this patch, so figuring out what is wrong with that will make me happy. :-)


  reply	other threads:[~2024-05-29 14:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 11:06 Depends-on Morten Brørup
2024-05-29 14:33 ` Depends-on Aaron Conole
2024-05-29 14:40   ` Morten Brørup [this message]
2024-05-31 21:22     ` Depends-on Patrick Robb
2024-06-03 18:48       ` Depends-on Aaron Conole

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=98CBD80474FA8B44BF855DF32C47DC35E9F4CE@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=aconole@redhat.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).