From: Michael Ellerman <michael@ellerman.id.au>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
Auke Kok <auke-jan.h.kok@intel.com>,
gregkh@suse.de, davem@davemloft.net, grundler@parisc-linux.org
Subject: Re: [PATCH] PCI: also read revision ID for sparc64, ppc, read class at the same time
Date: Tue, 12 Jun 2007 11:10:48 +1000 [thread overview]
Message-ID: <1181610648.17771.0.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <59594cddc7b5eb6e355fd01efef8ebcc@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
On Sun, 2007-06-10 at 14:17 +0200, Segher Boessenkool wrote:
> >> + dev->revision = get_int_prop(node, "revision-id", 0);
> >
> > It's not clear to me in the spec if nodes are required to have the
> > "revision-id" property.
>
> It is required for every PCI node.
Yep. I was reading the wrong spec :)
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-06-12 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 20:12 Auke Kok
2007-06-10 1:54 ` Grant Grundler
2007-06-22 17:12 ` Kok, Auke
2007-06-22 19:46 ` Greg KH
2007-06-10 11:24 ` Michael Ellerman
2007-06-10 12:17 ` Segher Boessenkool
2007-06-12 1:10 ` Michael Ellerman [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=1181610648.17771.0.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--cc=auke-jan.h.kok@intel.com \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=grundler@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®