From: "Marek Behún" <kabel@kernel.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, "Pali Rohár" <pali@kernel.org>
Subject: Re: [PATCH] dt-bindings: bus: add device tree bindings for fsl,p1021rdb-pc-cpld
Date: Wed, 6 Jul 2022 18:56:02 +0200 [thread overview]
Message-ID: <20220706185602.656f883a@thinkpad> (raw)
In-Reply-To: <CAL_Jsq+9H3YQgugiRpXsiLuHpfvKDYVSgLVsXq2kcbz-Uaqocg@mail.gmail.com>
On Tue, 5 Jul 2022 14:09:36 -0600
Rob Herring <robh+dt@kernel.org> wrote:
> Not really a simple-bus if it has registers to init/program the bus.
It doesn't.
Marek
next prev parent reply other threads:[~2022-07-06 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 17:54 [PATCH] dt-bindings: bus: add device tree bindings for fsl,p1021rdb-pc-cpld Marek Behún
2022-07-05 19:18 ` Rob Herring
2022-07-05 20:09 ` Rob Herring
2022-07-06 16:56 ` Marek Behún [this message]
2022-07-12 17:05 ` Rob Herring
2022-08-18 21:36 ` Pali Rohár
2022-08-31 11:46 ` Pali Rohár
2022-10-09 11:38 ` Pali Rohár
2022-11-01 22:27 ` Pali Rohár
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=20220706185602.656f883a@thinkpad \
--to=kabel@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=pali@kernel.org \
--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).