From: Neil Horman <nhorman@tuxdriver.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] relicense various bits of the dpdk
Date: Wed, 31 Jan 2018 20:49:29 -0500 [thread overview]
Message-ID: <20180201014929.GA13944@neilslaptop.think-freely.org> (raw)
In-Reply-To: <116736165.vppYjGxc5J@xps>
On Thu, Feb 01, 2018 at 01:31:34AM +0100, Thomas Monjalon wrote:
> 05/01/2018 11:53, Thomas Monjalon:
> > 04/12/2017 16:55, Neil Horman:
> > > +# SPDX-License-Identifier: BSD-3-Clause
> > > +# Copyright(c) 2015 Neil Horman. All rights reserved.
> > > +# Copyright(c) 2017 6WIND S.A.
> > > +# All rights reserved
> > [...]
> > > /*-
> > > - * BSD LICENSE
> > > + * SPDX-License-Identifier: BSD-3-Clause
> > > *
> > > * Copyright(c) 2015 Neil Horman <nhorman@tuxdriver.com>.
> > > * All rights reserved.
> > > *
> > > */
> >
> > Other SPDX headers use only one space after # or *,
> > and no empty line.
> >
> > Also, SPDX should be on the first line (except for scripts):
> > /* SPDX-License-Identifier: BSD-3-Clause
> >
> > Please, let's take this opportunity to have consistent headers.
> > Thanks
>
> Ping.
> Please could you do a v2?
> Thanks
>
Shoot, apologies, completely lost track of this, I'll take care of it in the morning
Neil
next prev parent reply other threads:[~2018-02-01 1:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 15:55 Neil Horman
2017-12-05 10:44 ` Hemant Agrawal
2018-01-05 10:53 ` Thomas Monjalon
2018-02-01 0:31 ` Thomas Monjalon
2018-02-01 1:49 ` Neil Horman [this message]
2018-02-01 12:19 ` [dpdk-dev] [PATCH v2] " Neil Horman
2018-02-01 12:49 ` Hemant Agrawal
2018-02-06 22:16 ` Thomas Monjalon
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=20180201014929.GA13944@neilslaptop.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=thomas@monjalon.net \
/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).