linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh+dt@kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] dt-bindings: pci: pci-msi: Correct the unit-address of the pci node name
Date: Thu, 1 Aug 2019 17:53:50 +0800	[thread overview]
Message-ID: <CAEUhbmVjELVPKwW6R+W+V2hQbZ_Zj_5j2ogjnTsuCwnK1pT-og@mail.gmail.com> (raw)
In-Reply-To: <1564306219-17439-2-git-send-email-bmeng.cn@gmail.com>

On Sun, Jul 28, 2019 at 5:30 PM Bin Meng <bmeng.cn@gmail.com> wrote:
>
> The unit-address must match the first address specified in the
> reg property of the node.
>
> Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
> ---
>
>  Documentation/devicetree/bindings/pci/pci-msi.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/pci/pci-msi.txt b/Documentation/devicetree/bindings/pci/pci-msi.txt
> index 9b3cc81..b73d839 100644
> --- a/Documentation/devicetree/bindings/pci/pci-msi.txt
> +++ b/Documentation/devicetree/bindings/pci/pci-msi.txt
> @@ -201,7 +201,7 @@ Example (5)
>                 #msi-cells = <1>;
>         };
>
> -       pci: pci@c {
> +       pci: pci@f {
>                 reg = <0xf 0x1>;
>                 compatible = "vendor,pcie-root-complex";
>                 device_type = "pci";
> --

Ping?

  reply	other threads:[~2019-08-01  9:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-28  9:30 [PATCH 1/2] dt-bindings: interrupt-controller: msi: Correct msi-controller@c's reg Bin Meng
2019-07-28  9:30 ` [PATCH 2/2] dt-bindings: pci: pci-msi: Correct the unit-address of the pci node name Bin Meng
2019-08-01  9:53   ` Bin Meng [this message]
2019-08-08  3:26     ` Bin Meng
2019-08-16 21:56   ` Rob Herring
2019-08-01  9:53 ` [PATCH 1/2] dt-bindings: interrupt-controller: msi: Correct msi-controller@c's reg Bin Meng
2019-08-08  3:25   ` Bin Meng
2019-08-16 21:54 ` Rob Herring
2020-03-13 14:05   ` Bin Meng
2020-03-30 18:43     ` 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=CAEUhbmVjELVPKwW6R+W+V2hQbZ_Zj_5j2ogjnTsuCwnK1pT-og@mail.gmail.com \
    --to=bmeng.cn@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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).