From: Kevin Traynor <ktraynor@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: web@dpdk.org, bluca@debian.org, thomas@monjalon.net,
christian.ehrhardt@canonical.com, xuemingl@nvidia.com
Subject: Re: [PATCH] release 21.11.3
Date: Tue, 20 Dec 2022 17:17:40 +0000 [thread overview]
Message-ID: <3724f024-78f5-4a40-7ba2-9e1d37d3980c@redhat.com> (raw)
In-Reply-To: <CAJFAV8xRqhROqNwczBh=7CyS_quF9Y_QnpRpG=7+0hxQ5yN40A@mail.gmail.com>
On 20/12/2022 17:11, David Marchand wrote:
> On Tue, Dec 20, 2022 at 5:15 PM Kevin Traynor <ktraynor@redhat.com> wrote:
>>
>> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
>
> Acked-by: David Marchand <david.marchand@redhat.com>
>
Thanks. Applied and pushed.
prev parent reply other threads:[~2022-12-20 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 16:15 Kevin Traynor
2022-12-20 17:11 ` David Marchand
2022-12-20 17:17 ` Kevin Traynor [this message]
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=3724f024-78f5-4a40-7ba2-9e1d37d3980c@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@redhat.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).