From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: NVMe: Invalid controller status value, device hotplug out
Date: Wed, 23 Jul 2014 07:24:04 -0700 [thread overview]
Message-ID: <53CFC584.2000301@linux.intel.com> (raw)
In-Reply-To: <1406049939-29310-1-git-send-email-mundu2510@gmail.com>
On 07/22/2014 10:25 AM, Mundu wrote:
> If device hotplug out, controller status become 0xFFFF_FFFF
> 1. Controller fatal status become true in nvme_kthread()
> 2. Ready bit nvere reset to 0 in nvme_wait_ready() for
> controller disable.
> above two scenarios controller status data is not a valid
> data, since device/controller is already removed (hotplug)
>
I believe you want this comment to be in the actual patch you sent??
The patch you sent after this email has no description, something
Matthew pointed out previously.
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
>
prev parent reply other threads:[~2014-07-23 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 17:25 NVMe: Invalid controller status value, device hotplug out Mundu
2014-07-22 17:25 ` [PATCH 1/1] If device hotplug out, controller status become 0xFFFF_FFFF 1. Controller fatal status become true in nvme_kthread() 2. Ready bit will not be reset to 0 in nvme_wait_ready() for controller disable above two scenarios controller status data is not a valid data, since device/controller is already removed (hotplug) Mundu
2014-07-22 17:40 ` Keith Busch
2014-07-22 17:57 ` mundu agarwal
2014-07-23 14:24 ` J Freyensee [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=53CFC584.2000301@linux.intel.com \
--to=james_p_freyensee@linux.intel.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.