From: Daniel Wagner <dwagner@suse.de>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: linux-nvme@lists.infradead.org, kbusch@kernel.org, gjoyce@ibm.com
Subject: Re: [PATCH libnvme] libnvme : record the nvme pci adapter physical slot
Date: Thu, 21 Mar 2024 14:48:16 +0100 [thread overview]
Message-ID: <l5plt4rl6hxyss4g6ucc73cn5qzntmqpecjzfdsumw7m7vq6f6@2maivyhuusl5> (raw)
In-Reply-To: <20240321132424.3362887-1-nilay@linux.ibm.com>
On Thu, Mar 21, 2024 at 06:46:17PM +0530, Nilay Shroff wrote:
> There is a subtle bug in the nvme controller physical
> slot lookup code due to which the readdir() prematurely
> aborts the lookup and hence libnvme fails to record the
> pci slot address of the nvme controller. This patch helps
> to fix this issue.
>
> Signed-off-by: Nilay Shroff <nilay@linux.ibm.com>
Patch applied. Thanks!
prev parent reply other threads:[~2024-03-21 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 13:16 [PATCH libnvme] libnvme : record the nvme pci adapter physical slot Nilay Shroff
2024-03-21 13:48 ` Daniel Wagner [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=l5plt4rl6hxyss4g6ucc73cn5qzntmqpecjzfdsumw7m7vq6f6@2maivyhuusl5 \
--to=dwagner@suse.de \
--cc=gjoyce@ibm.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).