All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Gurtovoy <maxg@mellanox.com>
To: Christoph Hellwig <hch@lst.de>, linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvmet: mark nvmet_ana_state static
Date: Tue, 12 May 2020 19:24:20 +0300	[thread overview]
Message-ID: <962c56fe-4530-43bf-4f95-c732b74b09c3@mellanox.com> (raw)
In-Reply-To: <20200512161926.1822603-1-hch@lst.de>


On 5/12/2020 7:19 PM, Christoph Hellwig wrote:
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>   drivers/nvme/target/configfs.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/nvme/target/configfs.c b/drivers/nvme/target/configfs.c
> index 19bd5e1c681ce..24eb4cf53b4f5 100644
> --- a/drivers/nvme/target/configfs.c
> +++ b/drivers/nvme/target/configfs.c
> @@ -1146,7 +1146,7 @@ static const struct config_item_type nvmet_referrals_type = {
>   	.ct_group_ops	= &nvmet_referral_group_ops,
>   };
>   
> -struct nvmet_type_name_map nvmet_ana_state[] = {
> +static struct nvmet_type_name_map nvmet_ana_state[] = {
>   	{ NVME_ANA_OPTIMIZED,		"optimized" },
>   	{ NVME_ANA_NONOPTIMIZED,	"non-optimized" },
>   	{ NVME_ANA_INACCESSIBLE,	"inaccessible" },


Looks good,

Reviewed-by: Max Gurtovoy <maxg@mellanox.com>



_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2020-05-12 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 16:19 [PATCH] nvmet: mark nvmet_ana_state static Christoph Hellwig
2020-05-12 16:24 ` Max Gurtovoy [this message]
2020-05-13  8:16   ` Chaitanya Kulkarni

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=962c56fe-4530-43bf-4f95-c732b74b09c3@mellanox.com \
    --to=maxg@mellanox.com \
    --cc=hch@lst.de \
    --cc=linux-nvme@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.