From: Alexander H Duyck <alexander.duyck@gmail.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
yhs@fb.com, Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v2] headers: Remove some left-over license text
Date: Thu, 22 Sep 2022 17:00:18 -0700 [thread overview]
Message-ID: <c6454874c531dd9e6c50c2110d47903b87a1e165.camel@gmail.com> (raw)
In-Reply-To: <88410cddd31197ea26840d7dd71612bece8c6acf.1663871981.git.christophe.jaillet@wanadoo.fr>
On Thu, 2022-09-22 at 20:41 +0200, Christophe JAILLET wrote:
> Remove some left-over from commit e2be04c7f995 ("License cleanup: add SPDX
> license identifier to uapi header files with a license")
>
> When the SPDX-License-Identifier tag has been added, the corresponding
> license text has not been removed.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> Changes since v1:
> - add tools/include/uapi/linux/tc_act/tc_bpf.h [Yonghong Song <yhs@fb.com>]
>
> v1: https://lore.kernel.org/all/2a15aba72497e78ff08c8b8a8bfe3cf5a3e6ee18.1662897019.git.christophe.jaillet@wanadoo.fr/
> ---
> include/uapi/linux/tc_act/tc_bpf.h | 5 -----
> include/uapi/linux/tc_act/tc_skbedit.h | 13 -------------
> include/uapi/linux/tc_act/tc_skbmod.h | 7 +------
> include/uapi/linux/tc_act/tc_tunnel_key.h | 5 -----
> include/uapi/linux/tc_act/tc_vlan.h | 5 -----
> tools/include/uapi/linux/tc_act/tc_bpf.h | 5 -----
> 6 files changed, 1 insertion(+), 39 deletions(-)
>
>
<snip>
> diff --git a/include/uapi/linux/tc_act/tc_skbedit.h b/include/uapi/linux/tc_act/tc_skbedit.h
> index 6cb6101208d0..64032513cc4c 100644
> --- a/include/uapi/linux/tc_act/tc_skbedit.h
> +++ b/include/uapi/linux/tc_act/tc_skbedit.h
> @@ -2,19 +2,6 @@
> /*
> * Copyright (c) 2008, Intel Corporation.
> *
> - * This program is free software; you can redistribute it and/or modify it
> - * under the terms and conditions of the GNU General Public License,
> - * version 2, as published by the Free Software Foundation.
> - *
> - * This program is distributed in the hope it will be useful, but WITHOUT
> - * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
> - * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
> - * more details.
> - *
> - * You should have received a copy of the GNU General Public License along with
> - * this program; if not, write to the Free Software Foundation, Inc., 59 Temple
> - * Place - Suite 330, Boston, MA 02111-1307 USA.
> - *
> * Author: Alexander Duyck <alexander.h.duyck@intel.com>
> */
>
Looks good to me.
Acked-by: Alexander Duyck <alexanderduyck@fb.com>
next prev parent reply other threads:[~2022-09-23 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 18:41 Christophe JAILLET
2022-09-23 0:00 ` Alexander H Duyck [this message]
2022-09-26 19:49 ` Jakub Kicinski
2022-09-27 7:59 ` Jiri Pirko
2022-09-27 11:15 ` Jamal Hadi Salim
2022-09-27 15:00 ` patchwork-bot+netdevbpf
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=c6454874c531dd9e6c50c2110d47903b87a1e165.camel@gmail.com \
--to=alexander.duyck@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yhs@fb.com \
/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
all inboxes | Powered by JetHome®