devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org
Subject: PCI Device Tree binding documentation links broken
Date: Tue, 20 Oct 2015 10:39:42 -0500	[thread overview]
Message-ID: <20151020153942.GE8224@localhost> (raw)

Hi Linus,

301d2d87cb4f ("Documentation/devicetree: add a small note on PCI")
added some useful links:

  +PCI Bus Binding to: IEEE Std 1275-1994
  +http://www.openfirmware.org/ofwg/bindings/pci/pci2_1.pdf

  +Open Firmware Recommended Practice: Interrupt Mapping
  +http://www.openfirmware.org/1275/practice/imap/imap0_9d.pdf

But both links are now broken.  I looked a little bit, but didn't find
anything that looked like a reliable source.  Do you know of anything
better?

Bjorn

             reply	other threads:[~2015-10-20 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 15:39 Bjorn Helgaas [this message]
2015-10-20 20:47 ` PCI Device Tree binding documentation links broken Rob Herring

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=20151020153942.GE8224@localhost \
    --to=helgaas@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).