All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: <linux-pci@vger.kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linasvepstas@gmail.com>,
	<bhelgaas@google.com>
Subject: Re: [PATCH] pci-error-recover: doc cleanup
Date: Thu, 8 Dec 2016 22:13:56 +0800	[thread overview]
Message-ID: <58496AA4.5030602@cn.fujitsu.com> (raw)
In-Reply-To: <20161208070539.0f00ce71@lwn.net>



On 12/08/2016 10:05 PM, Jonathan Corbet wrote:
> On Thu, 8 Dec 2016 16:16:14 +0800
> Cao jin <caoj.fnst@cn.fujitsu.com> wrote:
> 
>>  The platform resets the link, and then calls the link_reset() callback
>>  on all affected device drivers.  This is a PCI-Express specific state
>> -and is done whenever a non-fatal error has been detected that can be
>> +and is done whenever a fatal error has been detected that can be
>>  "solved" by resetting the link. This call informs the driver of the
> 
> As far as I can tell, the original text was correct here; why do you
> think this change needs to be made?
> 

See do_recovery() in aer core, reset_link() is called only seeing fatal
error.

-- 
Sincerely,
Cao jin



  reply	other threads:[~2016-12-08 14:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08  8:16 [PATCH] pci-error-recover: doc cleanup Cao jin
2016-12-08 14:05 ` Jonathan Corbet
2016-12-08 14:13   ` Cao jin [this message]
2016-12-09  6:24     ` Linas Vepstas
2016-12-09  6:37       ` Cao jin
2016-12-09  6:44         ` Linas Vepstas
2016-12-09  7:59           ` Cao jin
2016-12-09 16:11           ` Alex Williamson
2016-12-09 14:37         ` Jonathan Corbet
2016-12-19  3:25           ` Cao jin
2016-12-09  6:50       ` Andrew Donnellan
2016-12-14  2:39         ` Gavin Shan

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=58496AA4.5030602@cn.fujitsu.com \
    --to=caoj.fnst@cn.fujitsu.com \
    --cc=bhelgaas@google.com \
    --cc=corbet@lwn.net \
    --cc=linasvepstas@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.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.