From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
netfilter-devel@vger.kernel.org, linux-spdx@vger.kernel.org,
Manoj Basapathi <manojbm@codeaurora.org>,
Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
Subject: Re: netfilter: xtables: Bring SPDX identifier back
Date: Mon, 6 Jun 2022 19:01:11 +0200 [thread overview]
Message-ID: <Yp4y19o3EnRE+f7r@salvia> (raw)
In-Reply-To: <Yp4xrPVwI8g7glwr@kroah.com>
On Mon, Jun 06, 2022 at 06:56:12PM +0200, Greg KH wrote:
> On Mon, Jun 06, 2022 at 05:34:34PM +0200, Pablo Neira Ayuso wrote:
> > On Mon, Jun 06, 2022 at 05:23:45PM +0200, Thomas Gleixner wrote:
> > > Commit e2be04c7f995 ("License cleanup: add SPDX license identifier to
> > > uapi header files with a license") added the correct SPDX identifier to
> > > include/uapi/linux/netfilter/xt_IDLETIMER.h.
> > >
> > > A subsequent commit removed it for no reason and reintroduced the UAPI
> > > license incorrectness as the file is now missing the UAPI exception
> > > again.
> > >
> > > Add it back and remove the GPLv2 boilerplate while at it.
> >
> > LGTM.
> >
> > You handle this or I place this in the nf.git tree?
>
> If you want to take it, that's fine with me, otherwise I can in a
> spdx-specific tree that I manage.
I did not know there is a specific tree for this.
> Your choice, which ever is easier for you.
please take it
next prev parent reply other threads:[~2022-06-06 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 15:23 netfilter: xtables: Bring SPDX identifier back Thomas Gleixner
2022-06-06 15:34 ` Pablo Neira Ayuso
2022-06-06 16:56 ` Greg KH
2022-06-06 17:01 ` Pablo Neira Ayuso [this message]
2022-06-06 17:10 ` Greg KH
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=Yp4y19o3EnRE+f7r@salvia \
--to=pablo@netfilter.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-spdx@vger.kernel.org \
--cc=manojbm@codeaurora.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=subashab@codeaurora.org \
--cc=tglx@linutronix.de \
/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.