mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>
Subject: Re: [PATCH] headers: Remove some left-over license text in include/uapi/linux/hsi/
Date: Tue, 15 Nov 2022 07:48:51 +0100	[thread overview]
Message-ID: <Y3M2UxC+vpf9cgyU@kroah.com> (raw)
In-Reply-To: <20221114210155.anq5gkggfrvj6nki@mercury.elektranox.org>

On Mon, Nov 14, 2022 at 10:01:55PM +0100, Sebastian Reichel wrote:
> Hi,
> 
> On Sun, Sep 11, 2022 at 01:56:59PM +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>
> > ---
> 
> IIRC that was intentional, since the plan was to seek for an
> explicit Ack from the copyright holder when removing the text.

Did that ever happen?

> I've added Greg for clarification and hopefully the latest
> mail address from Kai and Peter.

It's fine to remove license "boilerplate" text like this, especially
when it is wrong (hint, is the FSF's address correct?).

thanks,

greg k-h

  reply	other threads:[~2022-11-15  6:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11 11:56 Christophe JAILLET
2022-11-14 21:01 ` Sebastian Reichel
2022-11-15  6:48   ` Greg Kroah-Hartman [this message]
2022-11-15 12:59   ` Péter Ujfalusi
2022-11-15 17:21   ` Kai Vehmanen

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=Y3M2UxC+vpf9cgyU@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=sebastian.reichel@collabora.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®