From: "Morten Brørup" <mb@smartsharesystems.com>
To: "David Marchand" <david.marchand@redhat.com>
Cc: <dev@dpdk.org>
Subject: RE: [RFC PATCH v2] net: 2-byte align packed headers
Date: Wed, 30 Oct 2024 16:15:16 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F853@smartserver.smartshare.dk> (raw)
In-Reply-To: <CAJFAV8w6qBCh8fY0PcQ4EENSLceqTP_-GRNe4Q6U0Md-BwT3xg@mail.gmail.com>
> From: David Marchand [mailto:david.marchand@redhat.com]
> Sent: Wednesday, 30 October 2024 16.11
>
> On Wed, Oct 30, 2024 at 1:55 PM Morten Brørup
> <mb@smartsharesystems.com> wrote:
> >
> > Recheck-request: rebase=main, iol-unit-amd64-testing
>
> There is a conflict because of a change in rte_ether.h and the
> rte_ip.h split into rte_ip4.h/rte_ip6.h (Robin series).
> Could you send a new revision?
Will do.
-Morten
next prev parent reply other threads:[~2024-10-30 15:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 13:19 [RFC PATCH] net: TEST " Morten Brørup
2024-10-11 16:06 ` [RFC PATCH v2] net: " Morten Brørup
2024-10-30 12:35 ` Morten Brørup
2024-10-30 12:52 ` David Marchand
2024-10-30 12:55 ` Morten Brørup
2024-10-30 15:10 ` David Marchand
2024-10-30 15:15 ` Morten Brørup [this message]
2024-10-30 12:42 ` Bruce Richardson
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=98CBD80474FA8B44BF855DF32C47DC35E9F853@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=david.marchand@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).