patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Robin Jarry <rjarry@redhat.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: please help backporting some patches to stable release 21.11.8
Date: Fri, 30 Aug 2024 10:04:10 +0100	[thread overview]
Message-ID: <50efb48e-63d2-4dae-b16f-ba6767024b11@redhat.com> (raw)
In-Reply-To: <D3SBR6L79NHF.26EVH8T00D9ZN@redhat.com>

On 29/08/2024 11:31, Robin Jarry wrote:
> Hi Kevin,
> 

Hi Robin,

> Kevin Traynor, Aug 29, 2024 at 12:21:
>> Can authors check your patches in the following list and either:
>>     - Backport your patches to the 21.11 branch, or
>>     - Indicate that the patch should not be backported
> [snip]
>> New backports with unresolved conflicts:
> [snip]
>> d5c8b6bb74  Robin Jarry      graph: fix ID collisions
> 
> rte_graph was still in its early stages in this branch. Backporting is 
> most likely not required. And fixing the conflicts without breaking 
> other things seems hard.
> 

That makes sense, I saw there was many conflicts. Will drop from list.

thanks,
Kevin.


  reply	other threads:[~2024-08-30  9:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29 10:21 Kevin Traynor
2024-08-29 10:31 ` Robin Jarry
2024-08-30  9:04   ` Kevin Traynor [this message]
2024-08-30  3:00 ` Ma, WenwuX
2024-08-30  9:01   ` Kevin Traynor
2024-08-30  9:16 ` Ye, MingjinX
2024-08-30  9:34   ` Kevin Traynor
2024-08-31 16:27 ` Stephen Hemminger
2024-09-03 13:25   ` Kevin Traynor
2024-08-31 16:42 ` Stephen Hemminger
2024-09-02  8:23   ` David Marchand
2024-09-02 15:50     ` Stephen Hemminger
2024-09-02 13:01 ` Etelson, Gregory
2024-09-03 13:25   ` Kevin Traynor

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=50efb48e-63d2-4dae-b16f-ba6767024b11@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=rjarry@redhat.com \
    --cc=stable@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).