From: Greg KH <greg@kroah.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: "Nguyen, Tom L" <tom.l.nguyen@intel.com>,
long <tlnguyen@snoqualmie.dp.intel.com>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH 0/6] PCI Express Advanced Error Reporting Driver
Date: Tue, 15 Mar 2005 18:24:04 -0800 [thread overview]
Message-ID: <20050316022404.GA13685@kroah.com> (raw)
In-Reply-To: <20050316021207.GA6608@colo.lackof.org>
On Tue, Mar 15, 2005 at 07:12:07PM -0700, Grant Grundler wrote:
> On Tue, Mar 15, 2005 at 01:11:39PM -0700, Grant Grundler wrote:
> > Tom,
> > A co-worker made the following observation (I'm paraphrasing):
> > ...this proposal does not deal with the Error Reporting ECN.
> > For example, they do not show the advisory non-fatal bit in
> > the correctable error status register.
> >
> > I believe he is referring to the "Error Clarifications ECN":
> >
> > http://www.pcisig.com/specifications/pciexpress/ECN_-_Error_Clarifications.pdf
>
> Tom,
> Sorry - I got this wrong.
> He was referring to an unpublished draft "Error Reporting ECN".
> You'll have to talk to Intel's PCI-SIG representative to get a copy.
> [ Ugh. And everyone else is SOL - sorry ]
Then we have no obligation to be compliant with a unpublished spec :)
greg k-h
next prev parent reply other threads:[~2005-03-16 2:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 18:33 [PATCH 5/6] PCI Express Advanced Error Reporting Driver Nguyen, Tom L
2005-03-12 0:10 ` [PATCH 0/6] " long
2005-03-12 7:20 ` Greg KH
2005-03-15 20:11 ` Grant Grundler
2005-03-16 2:12 ` Grant Grundler
2005-03-16 2:24 ` Greg KH [this message]
2005-03-18 18:26 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2005-03-18 18:44 Nguyen, Tom L
2005-03-15 22:41 Nguyen, Tom L
2005-03-15 21:54 Nguyen, Tom L
2005-03-15 22:38 ` Grant Grundler
2005-03-14 18:34 Nguyen, Tom L
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=20050316022404.GA13685@kroah.com \
--to=greg@kroah.com \
--cc=grundler@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=tlnguyen@snoqualmie.dp.intel.com \
--cc=tom.l.nguyen@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.