From: <Eugen.Hristev@microchip.com>
To: <robh@kernel.org>, <devicetree@vger.kernel.org>,
<devicetree-spec@vger.kernel.org>
Cc: <wsa+renesas@sang-engineering.com>, <dmitry.torokhov@gmail.com>,
<Codrin.Ciubotariu@microchip.com>, <jonathanh@nvidia.com>,
<alain.volmat@foss.st.com>, <matt@codeconstruct.com.au>
Subject: Re: [dtschema PATCH] schemas: i2c: Add missing properties and descriptions
Date: Tue, 7 Jun 2022 06:43:14 +0000 [thread overview]
Message-ID: <cc597d64-a7a9-0078-2d41-754a8d82af8a@microchip.com> (raw)
In-Reply-To: <20220427175956.362987-1-robh@kernel.org>
On 4/27/22 8:59 PM, Rob Herring wrote:
> Add remaining properties and descriptions from i2c.txt binding in Linux
> kernel tree. The Cc list are the authors of i2c.txt.
>
> Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>
> Cc: Eugen Hristev <eugen.hristev@microchip.com>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Cc: Codrin Ciubotariu <codrin.ciubotariu@microchip.com>
> Cc: Jon Hunter <jonathanh@nvidia.com>
> Cc: Alain Volmat <alain.volmat@foss.st.com>
> Cc: Matt Johnston <matt@codeconstruct.com.au>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> Cc list,
>
> I need your or your company's permission to relicense i2c.txt contents
> (used in 'description') to BSD-2-Clause. Please ack and provide a
> copyright if desired.
>
Acked-by: Eugen Hristev <eugen.hristev@microchip.com>
prev parent reply other threads:[~2022-06-07 6:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 17:59 [dtschema PATCH] schemas: i2c: Add missing properties and descriptions Rob Herring
2022-04-28 9:11 ` Matt Johnston
2022-06-01 15:00 ` Rob Herring
2022-06-01 21:29 ` Dmitry Torokhov
2022-06-03 14:41 ` Alain Volmat
2022-06-03 15:53 ` Wolfram Sang
2022-06-03 16:24 ` Rob Herring
2022-06-03 18:27 ` Wolfram Sang
2022-06-07 6:43 ` Eugen.Hristev [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=cc597d64-a7a9-0078-2d41-754a8d82af8a@microchip.com \
--to=eugen.hristev@microchip.com \
--cc=Codrin.Ciubotariu@microchip.com \
--cc=alain.volmat@foss.st.com \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=matt@codeconstruct.com.au \
--cc=robh@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 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).