From: Keith Busch <kbusch@kernel.org>
To: Daniel Wagner <dwagner@suse.de>
Cc: linux-nvme@lists.infradead.org, Ming Lei <ming.lei@redhat.com>,
Sagi Grimberg <sagi@grimberg.me>, Hannes Reinecke <hare@suse.de>,
Martin Wilck <martin.wilck@suse.com>,
Belanger Martin <Martin.Belanger@dell.com>,
James Smart <jsmart2021@gmail.com>,
Hanumanthu H <hanumanthuh@micron.com>
Subject: Re: nvme-cli license clarification
Date: Mon, 16 May 2022 10:21:03 -0600 [thread overview]
Message-ID: <YoJ574Sr5oOLSM8T@kbusch-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20220516161608.of4tklsysuvgbtie@carbon.lan>
On Mon, May 16, 2022 at 06:16:08PM +0200, Daniel Wagner wrote:
> 2. nvme.h
>
> The situation here is a bit simpler as Keith is 'owning' most
> of the lines (monolithic and master branch are almost identically)
>
> Copyright (c) 2011-2014, Intel Corporation
>
> 104 Keith Busch
> 26 Hannes Reinecke
> 6 Steven Seungcheol Lee
> 3 Sagi Grimberg
> 3 Christoph Hellwig
> 2 Scott Bauer
> 2 Minwoo Im
> 2 Martin Wilck
> 2 Daniel Wagner
> 1 Warner Losh
> 1 Tomasz Zawadzki
> 1 Ming Lin
> 1 Max Gurtovoy
> 1 Martin Belanger
> 1 Jeffrey Lien
> 1 James Smart
> 1 Brandon Paupore
>
> I suppose someone from Intel needs to signed of the 'or any later
> version' thing. Keith do you happen to have a contact for this?
I am not sure of who would be interested at Intel in this anymore. This was
initially just a copy of the Linux kernel's header, though, and diverged
significantly from there, but I guess we'd need to inherit the original's
GPLv2 only license?
next prev parent reply other threads:[~2022-05-16 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 16:16 nvme-cli license clarification Daniel Wagner
2022-05-16 16:21 ` Keith Busch [this message]
2022-05-17 7:57 ` Daniel Wagner
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=YoJ574Sr5oOLSM8T@kbusch-mbp.dhcp.thefacebook.com \
--to=kbusch@kernel.org \
--cc=Martin.Belanger@dell.com \
--cc=dwagner@suse.de \
--cc=hanumanthuh@micron.com \
--cc=hare@suse.de \
--cc=jsmart2021@gmail.com \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.wilck@suse.com \
--cc=ming.lei@redhat.com \
--cc=sagi@grimberg.me \
/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