From: Hannes Reinecke <hare@suse.de>
To: Max Gurtovoy <mgurtovoy@nvidia.com>,
hch@lst.de, sagi@grimberg.me, kbusch@kernel.org,
linux-nvme@lists.infradead.org, axboe@kernel.dk
Cc: oren@nvidia.com, israelr@nvidia.com
Subject: Re: [PATCH v2 1/1] nvme: move sysfs code to a dedicated sysfs.c file
Date: Wed, 26 Apr 2023 13:27:32 +0200 [thread overview]
Message-ID: <4010e880-b346-8268-e56c-d25cbec4bb0f@suse.de> (raw)
In-Reply-To: <20230424211242.19614-1-mgurtovoy@nvidia.com>
On 4/24/23 23:12, Max Gurtovoy 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.
>
> This patch does not include any functional changes.
>
> Reviewed-by: Keith Busch <kbusch@kernel.org>
> Signed-off-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> ---
>
> changes from v1:
> - rephrase the title from "nvme: add a dedicated .c file for sysfs interface" (Sagi)
> - add Reviewed-by signature from Keith
>
> changes from RFC:
> - Removed RCF tag
> - updated copyrights mistake
> - fix License copy/paste bug (Sagi)
>
> ---
> drivers/nvme/host/Makefile | 2 +-
> drivers/nvme/host/core.c | 650 +-----------------------------------
> drivers/nvme/host/nvme.h | 4 +
> drivers/nvme/host/sysfs.c | 655 +++++++++++++++++++++++++++++++++++++
> 4 files changed, 662 insertions(+), 649 deletions(-)
> create mode 100644 drivers/nvme/host/sysfs.c
>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
next prev parent reply other threads:[~2023-04-26 11:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 21:12 [PATCH v2 1/1] nvme: move sysfs code to a dedicated sysfs.c file Max Gurtovoy
2023-04-25 15:27 ` Jens Axboe
2023-05-01 14:48 ` Max Gurtovoy
2023-04-26 11:27 ` Hannes Reinecke [this message]
2023-05-12 20:32 ` Christoph Hellwig
2023-05-15 14:57 ` Keith Busch
2023-05-15 17:02 ` 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=4010e880-b346-8268-e56c-d25cbec4bb0f@suse.de \
--to=hare@suse.de \
--cc=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