All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Martin Wilck <mwilck@suse.com>
Cc: DM-DEVEL ML <dm-devel@redhat.com>
Subject: Re: [dm-devel] [PATCH] multipath-tools: add basic info on how to use multipath-tools with NVMe devices
Date: Mon, 28 Mar 2022 19:57:21 +0200	[thread overview]
Message-ID: <9bdd8437-741b-ff0c-068c-9d8cf211fff0@gmail.com> (raw)
In-Reply-To: <5187f68e1a6595d47d10a05ea01931e1ce8cad27.camel@suse.com>

On 3/28/22 19:48, Martin Wilck wrote:
> On Mon, 2022-03-28 at 19:04 +0200, Xose Vazquez Perez wrote:
>> Cc: Martin Wilck <mwilck@suse.com>
>> Cc: Benjamin Marzinski <bmarzins@redhat.com>
>> Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>
>> Cc: DM-DEVEL ML <dm-devel@redhat.com>
>> Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
>> ---
>>   README.nvme | 12 ++++++++++++
>>   1 file changed, 12 insertions(+)
>>   create mode 100644 README.nvme
> 
> Why another separate README with just 12 lines?
> 
> Martin

README.md is intended multipath-tools developers.
And README.alua and README.nvme are for sysadmins.

--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel

  reply	other threads:[~2022-03-28 18:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 17:04 [dm-devel] [PATCH] multipath-tools: add basic info on how to use multipath-tools with NVMe devices Xose Vazquez Perez
2022-03-28 17:48 ` Martin Wilck
2022-03-28 17:57   ` Xose Vazquez Perez [this message]
2022-04-01 10:20     ` Martin Wilck
2022-06-16 20:32       ` Xose Vazquez Perez
2022-06-17  6:48         ` Martin Wilck

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=9bdd8437-741b-ff0c-068c-9d8cf211fff0@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=dm-devel@redhat.com \
    --cc=mwilck@suse.com \
    /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.