devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: linuxarm@huawei.com, mauro.chehab@huawei.com,
	Binghui Wang <wangbinghui@hisilicon.com>,
	Xiaowei Song <songxiaowei@hisilicon.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Adjust HiKey examples for kirin-pcie
Date: Mon, 16 Aug 2021 15:34:37 -0500	[thread overview]
Message-ID: <YRrL3Y3wvMLYSUsZ@robh.at.kernel.org> (raw)
In-Reply-To: <cover.1629143524.git.mchehab+huawei@kernel.org>

On Mon, Aug 16, 2021 at 09:53:24PM +0200, Mauro Carvalho Chehab wrote:
> Rob,
> 
> As discussed on another thread, there are three issues at
> pci/hisilicon,kirin-pcie.yaml:
> 
> - The bus-range parameters are causing warnings;
> - The Kirin970 example doesn't reflect the right device
>   hierarchy, causing some of_node files under sysfs to
>   not be initialized;
> - There is a wrong msi-parent node causing it to not work
>   properly and to produce  several warnings.
> 
> This small series fix such issues.
> 
> Mauro Carvalho Chehab (2):
>   dt-bindings: PCI: kirin: fix bus-range
>   dt-bindings: PCI: kirin: fix HiKey970 example
> 
>  .../bindings/pci/hisilicon,kirin-pcie.yaml    | 66 ++++++++++---------
>  1 file changed, 36 insertions(+), 30 deletions(-)

I applied and squashed these into the prior series.

Rob

      parent reply	other threads:[~2021-08-16 20:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16 19:53 [PATCH v2 0/2] Adjust HiKey examples for kirin-pcie Mauro Carvalho Chehab
2021-08-16 19:53 ` [PATCH v2 1/2] dt-bindings: PCI: kirin: fix bus-range Mauro Carvalho Chehab
2021-08-16 19:53 ` [PATCH v2 2/2] dt-bindings: PCI: kirin: fix HiKey970 example Mauro Carvalho Chehab
2021-08-16 20:34 ` Rob Herring [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=YRrL3Y3wvMLYSUsZ@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=mauro.chehab@huawei.com \
    --cc=mchehab+huawei@kernel.org \
    --cc=songxiaowei@hisilicon.com \
    --cc=wangbinghui@hisilicon.com \
    /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).