From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] examples/l2fwd-event: add missing SPDX license header
Date: Thu, 28 Nov 2019 02:25:14 +0100 [thread overview]
Message-ID: <8848568.4o95eeWyW4@xps> (raw)
In-Reply-To: <CY4PR1801MB1863779398527A0100DB0C12DE740@CY4PR1801MB1863.namprd18.prod.outlook.com>
11/11/2019 14:21, Pavan Nikhilesh Bhagavatula:
> >Add same tag as other files in this example.
> >
> >Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
> Acked-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Applied, thanks
next prev parent reply other threads:[~2019-11-28 1:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 13:21 Pavan Nikhilesh Bhagavatula
2019-11-28 1:25 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-22 9:28 Hemant Agrawal
2019-11-08 17:09 Stephen Hemminger
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=8848568.4o95eeWyW4@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=pbhagavatula@marvell.com \
--cc=stephen@networkplumber.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).