From: Christoph Hellwig <hch@infradead.org>
To: Alex Talker <alextalker@yandex.ru>
Cc: maxg@mellanox.com, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme <linux-nvme@lists.infradead.org>
Subject: Re: nvme: Duplicate cntlid error
Date: Tue, 31 Mar 2020 06:24:21 -0700 [thread overview]
Message-ID: <20200331132421.GA27280@infradead.org> (raw)
In-Reply-To: <00875be1-c0bd-9b25-efa3-4236421678b7@yandex.ru>
On Tue, Mar 31, 2020 at 01:37:18PM +0300, Alex Talker wrote:
> but not in any MLNX OFED driver back-port. Does Mellanox has plans to
> include this feature in next release?
That is completely offtopic for this list. Also please don't use vendor
forks full of broken code, your life will be painful and of no
interest for others.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2020-03-31 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 11:44 nvme: Duplicate cntlid error Alex Talker
2020-03-31 6:45 ` Sagi Grimberg
2020-03-31 10:37 ` Alex Talker
2020-03-31 13:24 ` Christoph Hellwig [this message]
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=20200331132421.GA27280@infradead.org \
--to=hch@infradead.org \
--cc=alextalker@yandex.ru \
--cc=linux-nvme@lists.infradead.org \
--cc=maxg@mellanox.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