From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 19.11.10
Date: Wed, 11 Aug 2021 11:51:41 +0200 [thread overview]
Message-ID: <CAATJJ0JguEXuAN6FgQai8PM03cMwb6eufUdGSQj9fQ1DazgWgA@mail.gmail.com> (raw)
In-Reply-To: <20210811121009.16314dee@sovereign>
On Wed, Aug 11, 2021 at 11:10 AM Dmitry Kozlyuk
<dmitry.kozliuk@gmail.com> wrote:
>
> Hi Christian,
>
> 2021-08-10 17:39 (UTC+0200), christian.ehrhardt@canonical.com:
> > e9b3d79b06 Dmitry Kozlyuk bus: clarify log for non-NUMA-aware devices
>
> Will send an amended version.
Thanks in advance
> > e8c90926bd Dmitry Kozlyuk doc: fix build on Windows with Meson 0.58
>
> This patch isn't needed in DPDK 19.11.
And thanks for letting me know
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
next prev parent reply other threads:[~2021-08-11 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210810153941.749002-1-christian.ehrhardt@canonical.com>
2021-08-11 9:10 ` Dmitry Kozlyuk
2021-08-11 9:51 ` Christian Ehrhardt [this message]
2021-08-11 10:24 ` Lior Margalit
2021-08-11 11:24 ` Christian Ehrhardt
2021-08-13 1:29 ` Huisong Li
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=CAATJJ0JguEXuAN6FgQai8PM03cMwb6eufUdGSQj9fQ1DazgWgA@mail.gmail.com \
--to=christian.ehrhardt@canonical.com \
--cc=dmitry.kozliuk@gmail.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).