From: Greg KH <greg@kroah.com>
To: Kevin 'ldir' Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
Cc: "xiyou.wangcong@gmail.com" <xiyou.wangcong@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"jhs@mojatatu.com" <jhs@mojatatu.com>,
"jiri@resnulli.us" <jiri@resnulli.us>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"shuah@kernel.org" <shuah@kernel.org>
Subject: Re: [net-next v2] net: sched: Introduce act_ctinfo action
Date: Sun, 5 May 2019 12:23:14 +0200 [thread overview]
Message-ID: <20190505102314.GA12761@kroah.com> (raw)
In-Reply-To: <20190505101523.48425-1-ldir@darbyshire-bryant.me.uk>
On Sun, May 05, 2019 at 10:15:43AM +0000, Kevin 'ldir' Darbyshire-Bryant wrote:
> --- /dev/null
> +++ b/net/sched/act_ctinfo.c
> @@ -0,0 +1,407 @@
> +// SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note
How can a .c file, buried in the kernel tree, have a Linux-syscall-note
exception to it?
Are you _sure_ that is ok? That license should only be for files in the
uapi header directory.
thanks,
greg k-h
next prev parent reply other threads:[~2019-05-05 10:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 13:08 [PATCH net-next] net: sched: Introduce act_ctinfo action Kevin 'ldir' Darbyshire-Bryant
2019-04-30 21:47 ` Cong Wang
2019-05-03 21:20 ` Kevin 'ldir' Darbyshire-Bryant
2019-05-05 10:15 ` [net-next v2] " Kevin 'ldir' Darbyshire-Bryant
2019-05-05 10:23 ` Greg KH [this message]
2019-05-05 10:32 ` Kevin 'ldir' Darbyshire-Bryant
2019-05-05 10:43 ` Toke Høiland-Jørgensen
2019-05-05 13:20 ` [net-next v3] " Kevin 'ldir' Darbyshire-Bryant
2019-05-07 19:39 ` David Miller
2019-05-07 20:12 ` [PATCH net-next v4] " Kevin 'ldir' Darbyshire-Bryant
2019-05-08 0:20 ` David Miller
2019-05-08 16:12 ` Kevin 'ldir' Darbyshire-Bryant
2019-05-07 20:18 ` [net-next v3] " Kevin 'ldir' Darbyshire-Bryant
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=20190505102314.GA12761@kroah.com \
--to=greg@kroah.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=ldir@darbyshire-bryant.me.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).