From: Alexander Graf <agraf@suse.de>
To: Laszlo Ersek <lersek@redhat.com>,
peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hw/arm/virt: "bus-range"/end is off by one
Date: Fri, 13 Feb 2015 02:12:02 +0100 [thread overview]
Message-ID: <54DD4F62.4070302@suse.de> (raw)
In-Reply-To: <1423767013-22935-1-git-send-email-lersek@redhat.com>
On 12.02.15 19:50, Laszlo Ersek wrote:
> According to "PCI Bus Binding to IEEE Std 1275-1994", 3.1.2. Bus-specific
> Properties for Bus Nodes, the second integer in "bus-range" is an
> inclusive limit.
>
> This seems to be consistent with several *.dtsi files in the kernel tree,
> where examples like
>
> bus-range = <0 0>;
>
> are visible.
>
> In addition, the loop in gen_pci_parse_map_cfg_windows()
> [drivers/pci/host/pci-host-generic.c] uses "bus_range->end" as an
> inclusive limit.
>
> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
Nice catch!
Reviewed-by: Alexander Graf <agraf@suse.de>
Alex
next prev parent reply other threads:[~2015-02-13 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 18:50 [Qemu-devel] [PATCH] hw/arm/virt: "bus-range"/end is off by one Laszlo Ersek
2015-02-12 19:40 ` Wei Huang
2015-02-13 1:12 ` Alexander Graf [this message]
2015-02-13 1:13 ` Peter Maydell
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=54DD4F62.4070302@suse.de \
--to=agraf@suse.de \
--cc=lersek@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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.