From: Jens Axboe <axboe@kernel.dk>
To: Sagi Grimberg <sagi@grimberg.me>,
Max Gurtovoy <mgurtovoy@nvidia.com>,
hch@lst.de, kbusch@kernel.org, linux-nvme@lists.infradead.org
Cc: oren@nvidia.com, israelr@nvidia.com
Subject: Re: [RFC PATCH 1/1] nvme: add a dedicated .c file for sysfs interface
Date: Mon, 24 Apr 2023 07:56:13 -0600 [thread overview]
Message-ID: <980a8241-407f-a3eb-a1b9-d5eb1ae0ecf5@kernel.dk> (raw)
In-Reply-To: <ff1eb7b3-890a-7f12-94ad-6951bb1533ab@grimberg.me>
On 4/24/23 7:38?AM, Sagi Grimberg wrote:
>> diff --git a/drivers/nvme/host/sysfs.c b/drivers/nvme/host/sysfs.c
>> new file mode 100644
>> index 000000000000..8d2aabe2d290
>> --- /dev/null
>> +++ b/drivers/nvme/host/sysfs.c
>> @@ -0,0 +1,657 @@
>> +// SPDX-License-Identifier: GPL-2.0 OR Linux-OpenIB
>
> Linux-OpenIB ?
>
>> +/*
>> + * Sysfs interface for the NVMe core driver.
>> + *
>> + * Copyright (c) 2023, NVIDIA CORPORATION & AFFILIATES. All rights reserved.
>
> Not an expert in this matter, but does copy-pasting full hunk of code
> from one file to a new one qualify for copyrights claims?
IANAL, but that seems bogus for sure. Adding a copyright claim for just
moving code is nonsense.
--
Jens Axboe
next prev parent reply other threads:[~2023-04-24 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 13:03 [RFC PATCH 1/1] nvme: add a dedicated .c file for sysfs interface Max Gurtovoy
2023-04-24 13:38 ` Sagi Grimberg
2023-04-24 13:43 ` Max Gurtovoy
2023-04-24 13:56 ` Jens Axboe [this message]
2023-04-24 14:01 ` Max Gurtovoy
2023-04-24 14:04 ` Jens Axboe
2023-04-24 14:07 ` Max Gurtovoy
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=980a8241-407f-a3eb-a1b9-d5eb1ae0ecf5@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=israelr@nvidia.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mgurtovoy@nvidia.com \
--cc=oren@nvidia.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