Re: [PATCH] PCI: also read revision ID for sparc64, ppc, read class at the same time

+	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.

I guess 0 is a safe default though.

As good as any -- that is, no default is save.  0 should
be "good enough" here I guess.


Segher

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] PCI: also read revision ID for sparc64, ppc, read class at the same time
    • From: Michael Ellerman <[email protected]>

• References:
  • [PATCH] PCI: also read revision ID for sparc64, ppc, read class at the same time
    • From: Auke Kok <[email protected]>
  • Re: [PATCH] PCI: also read revision ID for sparc64, ppc, read class at the same time
    • From: Michael Ellerman <[email protected]>

• Prev by Date: [RFD] Documentation/stable_api_nonsense.txt translated into Japanese
• Next by Date: Re: [kvm-devel] [BUG] Oops with KVM-27
• Previous by thread: Re: [PATCH] PCI: also read revision ID for sparc64, ppc, read class at the same time
• Next by thread: Re: [PATCH] PCI: also read revision ID for sparc64, ppc, read class at the same time
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]