From: Christoph Hellwig <hch@infradead.org>
To: Prarit Bhargava <prarit@redhat.com>
Cc: 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 00:34:03 -0700 [thread overview]
Message-ID: <ZRKJa+cMsFxiizKb@infradead.org> (raw)
In-Reply-To: <6100798b-ab1d-262a-fd5b-435d6dfc4a53@redhat.com>
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.
next parent reply other threads:[~2023-09-26 7:34 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 ` Christoph Hellwig [this message]
2023-09-26 8:02 ` SPDX: Appletalk FW license in the kernel Greg KH
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=ZRKJa+cMsFxiizKb@infradead.org \
--to=hch@infradead.org \
--cc=davem@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).