DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Cc: jia.guo@intel.com
Subject: Re: [dpdk-dev] [PATCH] net/iavf: fix SPDX license text
Date: Thu, 19 Nov 2020 17:34:09 +0000	[thread overview]
Message-ID: <1953c5f4-38ba-db68-5469-6803ded2bddb@intel.com> (raw)
In-Reply-To: <f70c5dc8-1e9e-d09f-65c3-8e8238ff042a@intel.com>

On 11/16/2020 9:30 AM, Ferruh Yigit wrote:
> On 11/16/2020 2:14 AM, Stephen Hemminger wrote:
>> Obvious spelling error in SPDX license header.
>>
>> Fixes: 12b435bf8f2f ("net/iavf: support flex desc metadata extraction")
>> Cc: jia.guo@intel.com
>> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> 
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied to dpdk-next-net/main, thanks.

      reply	other threads:[~2020-11-19 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16  2:14 Stephen Hemminger
2020-11-16  9:30 ` Ferruh Yigit
2020-11-19 17:34   ` Ferruh Yigit [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=1953c5f4-38ba-db68-5469-6803ded2bddb@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=jia.guo@intel.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).