From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
dev@dpdk.org, stable@dpdk.org,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH] doc/prog_guide: fix missing SPDX license tag header
Date: Mon, 19 Oct 2020 18:40:35 +0200 [thread overview]
Message-ID: <3126187.ExpHmOiGIf@thomas> (raw)
In-Reply-To: <20200910122319.GH1789@bricha3-MOBL.ger.corp.intel.com>
10/09/2020 14:23, Bruce Richardson:
> On Thu, Sep 10, 2020 at 01:19:55PM +0100, Ferruh Yigit wrote:
> > On 9/10/2020 12:32 PM, Bruce Richardson wrote:
> > > The build-sdk-meson.rst file originates from the short plain-text meson
> > > instructions added in 2018. Add SPDX tag and copyright notice based on the
> > > original commit.
> > >
> > > Fixes: 9c3adc289c5e ("doc: add instructions on build using meson")
> > > Cc: stable@dpdk.org
> > >
> > > Reported-by: Stephen Hemminger <stephen@networkplumber.org>
> > > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > > ---
> > > --- a/doc/guides/prog_guide/build-sdk-meson.rst
> > > +++ b/doc/guides/prog_guide/build-sdk-meson.rst
> > > @@ -1,3 +1,6 @@
> > > +.. SPDX-License-Identifier: BSD-3-Clause
> > > + Copyright(c) 2018 Intel Corporation.
> >
> > Should copyright year be "2018 - 2020"? not sure. Other from that,
> >
> > Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Neither am I, but no major updates have been made to the file since 2018,
> so I'll keep it as-is.
Applied, thanks
prev parent reply other threads:[~2020-10-19 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 11:32 [dpdk-dev] [PATCH] doc/prog_guide: fix missing SPDX license tag header Bruce Richardson
2020-09-10 12:19 ` Ferruh Yigit
2020-09-10 12:23 ` Bruce Richardson
2020-10-19 16:40 ` Thomas Monjalon [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=3126187.ExpHmOiGIf@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stable@dpdk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.