From: Kevin Traynor <ktraynor@redhat.com>
To: "Niklas Söderlund" <niklas.soderlund@corigine.com>
Cc: dpdk stable <stable@dpdk.org>, Luca Boccassi <bluca@debian.org>
Subject: Re: please help backporting some patches to stable release 21.11.2
Date: Fri, 1 Jul 2022 17:06:42 +0100 [thread overview]
Message-ID: <CAOqxxS0uH73FL63OE=_sBNk5o2tsU9v5f-b2NZRNS_u6g+VF8A@mail.gmail.com> (raw)
In-Reply-To: <YrwoSKs4bpx5thFw@oden.dyn.berto.se>
On Wed, Jun 29, 2022 at 11:24 AM Niklas Söderlund
<niklas.soderlund@corigine.com> wrote:
>
> Hi Kevin,
>
> Thanks for your work!
>
> On 2022-06-24 17:31:08 +0100, Kevin Traynor wrote:
> > 417be15e5f Peng Zhang net/nfp: make sure MTU is never larger than mbuf size
>
> I see this patch already in the 21.11 branch as
>
> commit 1c770fda6f6f3862 ("net/nfp: make sure MTU is never larger than mbuf size")
>
> Is this patch picked up twice by the tooling since it had special care
> in [1]? Or is it some action I need to take here that I'm missing?
>
Hi Niklas. No action needed, it was just my mistake to not remove this
from this failed-to-apply list when I backported the 3 nfp commits. As
you say, it is now pushed to the 21.11 branch as part of the nfp
trilogy :-)
thanks,
Kevin.
bf7aa26ddd net/nfp: fix initialization
1c770fda6f net/nfp: make sure MTU is never larger than mbuf size
fe2cddeb08 net/nfp: update how max MTU is read
>
> 1. http://mails.dpdk.org/archives/stable/2022-June/039130.html
>
> --
> Kind Regards,
> Niklas Söderlund
>
next prev parent reply other threads:[~2022-07-01 16:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 16:31 Kevin Traynor
2022-06-27 9:15 ` Stanisław Kardach
2022-06-28 14:14 ` Kevin Traynor
2022-06-27 13:39 ` Rahul Lakkireddy
2022-06-28 14:18 ` Kevin Traynor
2022-06-27 21:15 ` McDaniel, Timothy
2022-06-28 14:13 ` Kevin Traynor
2022-06-28 14:20 ` Kevin Traynor
2022-06-29 10:24 ` Niklas Söderlund
2022-07-01 16:06 ` Kevin Traynor [this message]
2022-07-06 20:40 ` luca.boccassi
2022-08-01 13:31 ` McDaniel, Timothy
-- strict thread matches above, loose matches on Subject: below --
2022-06-21 10:02 Kevin Traynor
2022-06-22 2:57 ` Jiawen Wu
2022-06-22 4:26 ` Gagandeep Singh
2022-06-23 14:08 ` Kevin Traynor
2022-06-22 4:47 ` Zhou, YidingX
2022-06-22 8:40 ` Kalesh Anakkur Purayil
2022-06-22 10:48 ` Niklas Söderlund
2022-06-24 14:17 ` Kevin Traynor
[not found] ` <62b2851c.1c69fb81.cf480.7398SMTPIN_ADDED_BROKEN@mx.google.com>
2022-06-23 14:05 ` Kevin Traynor
2022-05-10 13:00 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='CAOqxxS0uH73FL63OE=_sBNk5o2tsU9v5f-b2NZRNS_u6g+VF8A@mail.gmail.com' \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=niklas.soderlund@corigine.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).