From: Rob Herring <robh@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-i2c@vger.kernel.org,
devicetree-spec@vger.kernel.org
Subject: Re: [PATCH v2 dt-schema 0/3] schemas: i2c: fix "smbus_alert" handling
Date: Thu, 15 Aug 2024 16:48:35 -0600 [thread overview]
Message-ID: <20240815224835.GA3287461-robh@kernel.org> (raw)
In-Reply-To: <20240815214013.6519-1-wsa+renesas@sang-engineering.com>
On Thu, Aug 15, 2024 at 11:40:10PM +0200, Wolfram Sang wrote:
> "smbus_alert" is currently listed as an interrupt for targets. This is
> wrong, it is an interrupt for the controller. The mistake (mea culpa!)
> was already in the originating "i2c.txt" file in the Linux Kernel. Time
> to fix it. Make small changes to descriptions to use inclusive language
> while we are here.
>
> Changes since v1:
> * use "contains" instead of "items" in patch 2+3
> * drop "irq" binding from patch 3
> * checked with dt-doc-validate now
>
> Thanks, Rob, for the support!
>
>
> Wolfram Sang (3):
> schemas: i2c: reword descriptions for inclusive language
> schemas: i2c: clean up interrupt descriptions for I2C targets
> schemas: i2c: add generic interrupt name for I2C controllers
Applied, thanks!
Rob
prev parent reply other threads:[~2024-08-15 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 21:40 [PATCH v2 dt-schema 0/3] schemas: i2c: fix "smbus_alert" handling Wolfram Sang
2024-08-15 21:40 ` [PATCH v2 dt-schema 1/3] schemas: i2c: reword descriptions for inclusive language Wolfram Sang
2024-08-15 21:40 ` [PATCH v2 dt-schema 2/3] schemas: i2c: clean up interrupt descriptions for I2C targets Wolfram Sang
2024-08-15 21:40 ` [PATCH v2 dt-schema 3/3] schemas: i2c: add generic interrupt name for I2C controllers Wolfram Sang
2024-08-15 22:48 ` 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=20240815224835.GA3287461-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree-spec@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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 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.