From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: "kbusch@kernel.org" <kbusch@kernel.org>,
"hch@lst.de" <hch@lst.de>,
"james.smart@broadcom.com" <james.smart@broadcom.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>
Subject: Re: [PATCH 2/2] nvmet: add module description to stop warnings
Date: Thu, 18 Jan 2024 18:28:13 +0000 [thread overview]
Message-ID: <8fc2dcae-e443-4367-b425-b073a073af2c@nvidia.com> (raw)
In-Reply-To: <45f0e4a1-f7f7-4b85-8a18-3793dd779365@grimberg.me>
> NVMe target TCP transport target ?
>
>> MODULE_LICENSE("GPL v2");
>> MODULE_ALIAS("nvmet-transport-3"); /* 3 == NVMF_TRTYPE_TCP */
>
will send out V2 with your suggestions ...
-ck
next prev parent reply other threads:[~2024-01-18 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 5:36 [PATCH 1/2] nvme: add module description to stop warnings Chaitanya Kulkarni
2024-01-18 5:36 ` [PATCH 2/2] nvmet: " Chaitanya Kulkarni
2024-01-18 12:26 ` Sagi Grimberg
2024-01-18 18:28 ` Chaitanya Kulkarni [this message]
2024-01-18 12:24 ` [PATCH 1/2] nvme: " Sagi Grimberg
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=8fc2dcae-e443-4367-b425-b073a073af2c@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--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