From: Bjorn Helgaas <helgaas@kernel.org>
To: "Alex G." <mr.nuke.me@gmail.com>
Cc: Alex_Gagniuc@dellteam.com, linux-pci@vger.kernel.org,
linux-nvme@lists.infradead.org, okaya@codeaurora.org,
Austin.Bolen@dell.com, Shyam.Iyer@dell.com,
keith.busch@intel.com, linux-pci-owner@vger.kernel.org
Subject: Re: AER: Malformed TLP recovery deadlock with NVMe drives
Date: Tue, 8 May 2018 13:01:35 -0500 [thread overview]
Message-ID: <20180508180135.GM161390@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <bb358683-79fc-0590-eb93-70f4c3c922da@gmail.com>
On Tue, May 08, 2018 at 12:32:28PM -0500, Alex G. wrote:
> On 05/08/2018 11:58 AM, Bjorn Helgaas wrote:
> > (looks like maybe colorizing escape sequences?).
>
> You mean the ANSI escape sequences. wget and cat in a color terminal.
> You will get so used to this, you will love it so much, you won't ever
> again want to open a a web page.
Hey, you're right! If I download it and look at it with "less", it *is*
pretty! It'd be cool if Chrome would do that. Maybe.
I'm really glad you're looking at this stuff and raising issues. I'm not
at all confident in the correctness or robustness of this code.
Bjorn
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: helgaas@kernel.org (Bjorn Helgaas)
Subject: AER: Malformed TLP recovery deadlock with NVMe drives
Date: Tue, 8 May 2018 13:01:35 -0500 [thread overview]
Message-ID: <20180508180135.GM161390@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <bb358683-79fc-0590-eb93-70f4c3c922da@gmail.com>
On Tue, May 08, 2018@12:32:28PM -0500, Alex G. wrote:
> On 05/08/2018 11:58 AM, Bjorn Helgaas wrote:
> > (looks like maybe colorizing escape sequences?).
>
> You mean the ANSI escape sequences. wget and cat in a color terminal.
> You will get so used to this, you will love it so much, you won't ever
> again want to open a a web page.
Hey, you're right! If I download it and look at it with "less", it *is*
pretty! It'd be cool if Chrome would do that. Maybe.
I'm really glad you're looking at this stuff and raising issues. I'm not
at all confident in the correctness or robustness of this code.
Bjorn
next prev parent reply other threads:[~2018-05-08 18:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 18:36 AER: Malformed TLP recovery deadlock with NVMe drives Alex G.
2018-05-07 18:36 ` Alex G.
2018-05-07 18:46 ` okaya
2018-05-07 18:46 ` okaya
2018-05-07 20:16 ` Alex G.
2018-05-07 20:16 ` Alex G.
2018-05-07 20:30 ` okaya
2018-05-07 20:30 ` okaya
2018-05-07 20:58 ` Alex G.
2018-05-07 20:58 ` Alex G.
2018-05-07 21:48 ` Sinan Kaya
2018-05-07 21:48 ` Sinan Kaya
2018-05-07 22:45 ` okaya
2018-05-07 22:45 ` okaya
2018-05-07 23:57 ` Alex_Gagniuc
2018-05-07 23:57 ` Alex_Gagniuc
2018-05-08 0:21 ` okaya
2018-05-08 0:21 ` okaya
2018-05-08 16:58 ` Bjorn Helgaas
2018-05-08 16:58 ` Bjorn Helgaas
2018-05-08 17:32 ` Alex G.
2018-05-08 17:32 ` Alex G.
2018-05-08 18:01 ` Bjorn Helgaas [this message]
2018-05-08 18:01 ` Bjorn Helgaas
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=20180508180135.GM161390@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=Alex_Gagniuc@dellteam.com \
--cc=Austin.Bolen@dell.com \
--cc=Shyam.Iyer@dell.com \
--cc=keith.busch@intel.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci-owner@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mr.nuke.me@gmail.com \
--cc=okaya@codeaurora.org \
/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.