public inbox for linux-spdx@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Prarit Bhargava <prarit@redhat.com>,
	Dave Miller <davem@redhat.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	jschlst@samba.org, linux-kernel <linux-kernel@vger.kernel.org>,
	linux-spdx@vger.kernel.org
Subject: Re: SPDX: Appletalk FW license in the kernel
Date: Tue, 26 Sep 2023 10:02:30 +0200	[thread overview]
Message-ID: <2023092606-fiction-finlike-97a5@gregkh> (raw)
In-Reply-To: <ZRKJa+cMsFxiizKb@infradead.org>

On Tue, Sep 26, 2023 at 12:34:03AM -0700, Christoph Hellwig wrote:
> On Fri, Sep 15, 2023 at 09:39:05AM -0400, Prarit Bhargava wrote:
> > To be clear, I am not asking for their removal, however, I do think a better
> > license should be issued for these files.  The files were trivially modified
> > in 2006. It could be that the code in question is now unused and it is just
> > easier to remove them.
> > 
> > Is there anyone you know of that we could approach to determine a proper
> > SPDX License for these files?
> 
> The code contains firmware that is downloaded to the device.  The proper
> thing would be to convert them to separate binary files in the
> linux-firmware packages.  But given that the driver has seen nothing
> but tree wide cleanups since the dawn of git I suspect there is no
> maintainer and probably no user left.  The best might be to indeed just
> remove it and see if anyone screams, in which case we could bring it
> back after doing the above.
> 

We should just remove them for now, I have no objection to that at all.

Want me to send the patch?

thanks,

greg k-h

  reply	other threads:[~2023-09-26  8:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6100798b-ab1d-262a-fd5b-435d6dfc4a53@redhat.com>
2023-09-26  7:34 ` SPDX: Appletalk FW license in the kernel Christoph Hellwig
2023-09-26  8:02   ` Greg KH [this message]
2023-09-26 13:49     ` Prarit Bhargava
2023-09-26 15:45   ` J Lovejoy

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=2023092606-fiction-finlike-97a5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@redhat.com \
    --cc=hch@infradead.org \
    --cc=jschlst@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=prarit@redhat.com \
    --cc=vkuznets@redhat.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