public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Max Gurtovoy <mgurtovoy@nvidia.com>
To: Sagi Grimberg <sagi@grimberg.me>,
	hch@lst.de, kbusch@kernel.org, linux-nvme@lists.infradead.org
Cc: axboe@kernel.dk, 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 16:43:58 +0300	[thread overview]
Message-ID: <b7800cad-841b-00a0-b51a-1f04502e8b99@nvidia.com> (raw)
In-Reply-To: <ff1eb7b3-890a-7f12-94ad-6951bb1533ab@grimberg.me>



On 24/04/2023 16:38, Sagi Grimberg wrote:
> 
>> The core.c file became long and hard to maintain. Create a dedicated
>> file to centralize the sysfs functionality. This is a common practice to
>> separate sysfs/configfs related logic from the main driver logic .c file.
>> For example, in the nvmet module the configfs interface has its own
>> dedicated file.
> 
> Don't mind having it..
> 
> [...]
> 
>> 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 ?
> 
copy/paste bug.

should be only // SPDX-License-Identifier: GPL-2.0

>> +/*
>> + * 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?

I'm not an expert as well. I'll remove it. Don't really care )


  reply	other threads:[~2023-04-24 13:44 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 [this message]
2023-04-24 13:56   ` Jens Axboe
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=b7800cad-841b-00a0-b51a-1f04502e8b99@nvidia.com \
    --to=mgurtovoy@nvidia.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=israelr@nvidia.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --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