mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Meneghini <jmeneghi@redhat.com>
To: Bryan Gurney <bgurney@redhat.com>,
	linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
	kbusch@kernel.org, hch@lst.de, sagi@grimberg.me, axboe@kernel.dk
Cc: bmarzins@redhat.com
Subject: Re: [PATCH] nvme: remove multipath module parameter
Date: Tue, 18 Feb 2025 11:41:56 -0500	[thread overview]
Message-ID: <03bd60e5-7c7b-4589-a71a-a48ff53a619c@redhat.com> (raw)
In-Reply-To: <b37a4f6c-95a9-430d-89f9-141b72fd6be8@redhat.com>

On 2/18/25 9:26 AM, John Meneghini wrote:
>> +    } else {
>> +#ifdef CONFIG_NVME_MULTIPATH
>>           sprintf(disk->disk_name, "nvme%dn%d", ctrl->subsys->instance,
>>               ns->head->instance);
>> -    } else {
>  > +#else
> 
> You don't need the this #ifdef conditional statement because the nvme_ns_head_multipath() function checks CONFIG_NVME_MULTIPATH
> for you and the sprintf(disk->disk_name, "nvme%dn%d" statement is kind of redundant.
> 
> 
>>           sprintf(disk->disk_name, "nvme%dn%d", ctrl->instance,
>>               ns->head->instance);
>> +#endif 

Actually, I think I may be wrong about this.  To maintain 100% backward compatibility with what the users see in the dmesg log, I think we need this code.

/John


  reply	other threads:[~2025-02-18 16:42 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 21:11 Bryan Gurney
2025-02-13 20:37 ` John Meneghini
2025-02-17  8:08   ` Sagi Grimberg
2025-02-17 16:14     ` John Meneghini
2025-02-18  8:19       ` Sagi Grimberg
2025-02-18 14:05         ` John Meneghini
2025-02-18 14:57           ` John Meneghini
2025-02-18 15:06   ` Keith Busch
2025-02-18 16:31     ` John Meneghini
2025-02-18 17:15       ` Keith Busch
2025-02-18 23:06         ` John Meneghini
2025-02-18 23:30           ` Keith Busch
2025-02-19 14:47         ` Nilay Shroff
2025-02-20 11:05           ` Sagi Grimberg
2025-02-20 16:47             ` Keith Busch
2025-02-26  9:55               ` Hannes Reinecke
2025-03-05 14:15                 ` Christoph Hellwig
2025-03-05 15:17                   ` Keith Busch
2025-03-05 23:51                     ` Christoph Hellwig
2025-03-05 23:57                       ` Keith Busch
2025-03-06  0:03                         ` Christoph Hellwig
2025-03-06  0:15                           ` Keith Busch
2025-03-06  7:12                           ` Hannes Reinecke
2025-03-06 14:18                             ` Christoph Hellwig
2025-03-06 15:01                               ` Keith Busch
2025-03-06 15:16                                 ` Christoph Hellwig
2025-03-07  0:46                                   ` Keith Busch
2025-03-07 15:19                                     ` Nilay Shroff
2025-03-07 15:43                                       ` Keith Busch
2025-03-09 17:23                                         ` Nilay Shroff
2025-03-10 13:29                                           ` Christoph Hellwig
2025-03-12  3:47                                           ` John Meneghini
2025-03-12 15:26                                             ` Nilay Shroff
2025-03-10 13:28                                     ` Christoph Hellwig
2025-03-12  3:08                 ` John Meneghini
2025-02-18 14:26 ` John Meneghini
2025-02-18 16:41   ` John Meneghini [this message]
2025-02-18 14:43 ` John Meneghini

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=03bd60e5-7c7b-4589-a71a-a48ff53a619c@redhat.com \
    --to=jmeneghi@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=bgurney@redhat.com \
    --cc=bmarzins@redhat.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®