From: Rob Herring <robh@kernel.org>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: alexandre.belloni@bootlin.com, linux-kernel@vger.kernel.org,
codrin.ciubotariu@microchip.com, ludovic.desroches@microchip.com,
linux-i2c@vger.kernel.org, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
nicolas.ferre@microchip.com, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: i2c: at91: Extend compatible list for lan966x
Date: Fri, 22 Oct 2021 18:37:38 -0500 [thread overview]
Message-ID: <YXNLQlUKgloigEd8@robh.at.kernel.org> (raw)
In-Reply-To: <20211012140718.2138278-2-horatiu.vultur@microchip.com>
On Tue, 12 Oct 2021 16:07:17 +0200, Horatiu Vultur wrote:
> Extend compatible list and the i2c-sda-hold-time-ns property
> with 'microchip,lan966x-i2c'
>
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
> Documentation/devicetree/bindings/i2c/i2c-at91.txt | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-10-22 23:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 14:07 [PATCH 0/2] i2c: at91: Add support for programmable clock source Horatiu Vultur
2021-10-12 14:07 ` [PATCH 1/2] dt-bindings: i2c: at91: Extend compatible list for lan966x Horatiu Vultur
2021-10-22 23:37 ` Rob Herring [this message]
2021-10-12 14:07 ` [PATCH 2/2] i2c: at91: add support for brsrcclk Horatiu Vultur
2021-10-13 8:49 ` [PATCH 0/2] i2c: at91: Add support for programmable clock source Codrin.Ciubotariu
2021-10-13 11:41 ` Horatiu Vultur - M31836
2021-10-13 13:10 ` Codrin.Ciubotariu
2021-11-05 21:47 ` Wolfram Sang
2021-11-08 8:35 ` Codrin.Ciubotariu
2021-11-08 9:29 ` Horatiu Vultur - M31836
2021-11-29 10:06 ` Wolfram Sang
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=YXNLQlUKgloigEd8@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=codrin.ciubotariu@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.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).