From: Rob Herring <robh@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, Paul Cercueil <paul@crapouillou.net>
Subject: Re: [PATCH] dt-bindings: ingenic,i2c: Rework interrupts in example
Date: Sun, 23 Jan 2022 09:28:54 -0600 [thread overview]
Message-ID: <Ye10NsR8MYHhUDwX@robh.at.kernel.org> (raw)
In-Reply-To: <20220119174349.3809513-1-robh@kernel.org>
On Wed, 19 Jan 2022 11:43:49 -0600, Rob Herring wrote:
> In order to determine the number of interrupt cells in examples, the
> examples will require all 'interrupts' properties to use the same number
> of cells or have explicit interrupt provider node(s). As the former is
> simpler, update the Ingenic example to use 2 interrupt cells everywhere.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> Documentation/devicetree/bindings/i2c/ingenic,i2c.yaml | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2022-01-23 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 17:43 [PATCH] dt-bindings: ingenic,i2c: Rework interrupts in example Rob Herring
2022-01-23 15:28 ` 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=Ye10NsR8MYHhUDwX@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@crapouillou.net \
/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).