From: Joel Stanley <joel@jms.id.au>
To: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
Cc: Andrew Jeffery <andrew@aj.id.au>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH dev-5.4] peci: fix license identifier
Date: Tue, 11 Feb 2020 22:52:14 +0000 [thread overview]
Message-ID: <CACPK8Xdb+gMZgEo-kCOBnjQtEMiPWoc5QJ7fF5W7ZeAOWzP6Og@mail.gmail.com> (raw)
In-Reply-To: <20200211224345.3624-1-jae.hyun.yoo@linux.intel.com>
On Tue, 11 Feb 2020 at 22:41, Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com> wrote:
>
> This commit fixes license identifier to prevent an error while
> doing 'make headers_install' that says:
> error: include/uapi/linux/peci-ioctl.h: missing "WITH Linux-syscall-note" for SPDX-License-Identifier
>
> Reported-by: Tao Ren <rentao.bupt@gmail.com>
> Signed-off-by: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
Thakns for the patch.
How's the upstream submission of PECI going?
> ---
> include/uapi/linux/peci-ioctl.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/uapi/linux/peci-ioctl.h b/include/uapi/linux/peci-ioctl.h
> index 843930f9fedd..c74b3cde52e8 100644
> --- a/include/uapi/linux/peci-ioctl.h
> +++ b/include/uapi/linux/peci-ioctl.h
> @@ -1,5 +1,5 @@
> -/* SPDX-License-Identifier: GPL-2.0 */
> -/* Copyright (c) 2018-2019 Intel Corporation */
> +/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
> +/* Copyright (c) 2018-2020 Intel Corporation */
>
> #ifndef __PECI_IOCTL_H
> #define __PECI_IOCTL_H
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-02-11 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 22:43 [PATCH dev-5.4] peci: fix license identifier Jae Hyun Yoo
2020-02-11 22:52 ` Joel Stanley [this message]
2020-02-11 22:56 ` Jae Hyun Yoo
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=CACPK8Xdb+gMZgEo-kCOBnjQtEMiPWoc5QJ7fF5W7ZeAOWzP6Og@mail.gmail.com \
--to=joel@jms.id.au \
--cc=andrew@aj.id.au \
--cc=jae.hyun.yoo@linux.intel.com \
--cc=openbmc@lists.ozlabs.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.