From: Thomas Monjalon <thomas@monjalon.net>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: David Marchand <david.marchand@redhat.com>,
web@dpdk.org, Luca Boccassi <bluca@debian.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-web] [PATCH] release 18.11.3
Date: Fri, 25 Oct 2019 15:15:17 +0200 [thread overview]
Message-ID: <2279091.fe13vJ1zpW@xps> (raw)
In-Reply-To: <CAJFAV8zaxf0cLVw6kqSNK5SFchVWvJzh9W2YfAyK6oO1eGfSgg@mail.gmail.com>
25/10/2019 14:51, David Marchand:
> On Fri, Oct 25, 2019 at 2:40 PM Kevin Traynor <ktraynor@redhat.com> wrote:
> >
> > Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
>
> Reviewed-by: David Marchand <david.marchand@redhat.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
Thanks
next prev parent reply other threads:[~2019-10-25 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 12:39 Kevin Traynor
2019-10-25 12:51 ` David Marchand
2019-10-25 13:15 ` Thomas Monjalon [this message]
2019-10-25 16:13 ` 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=2279091.fe13vJ1zpW@xps \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=ktraynor@redhat.com \
--cc=web@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).