From: Matthias Brugger <matthias.bgg@gmail.com>
To: Rob Herring <robh@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Wolfram Sang <wsa@the-dreams.de>
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
adamboardman@gmail.com
Subject: Re: [PATCH 1/4] dt-bindings: i2c: Document I2C controller binding for MT6797 SoC
Date: Fri, 15 May 2020 16:48:28 +0200 [thread overview]
Message-ID: <aa9ea456-dbee-229c-aea0-4860c6eb7adf@gmail.com> (raw)
In-Reply-To: <20200226222330.GA9392@bogus>
Hi Wolfram,
On 26/02/2020 23:23, Rob Herring wrote:
> On Sat, 22 Feb 2020 21:54:41 +0530, Manivannan Sadhasivam wrote:
>> I2C controller driver for MT6577 SoC is reused for MT6797 SoC. Hence,
>> document that in DT binding.
>>
>> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
>> ---
>> Documentation/devicetree/bindings/i2c/i2c-mt65xx.txt | 1 +
>> 1 file changed, 1 insertion(+)
>>
>
> Acked-by: Rob Herring <robh@kernel.org>
>
Do you want to take this thorough your tree or are you OK if I take it thorough
mine?
Regards,
Matthias
next prev parent reply other threads:[~2020-05-15 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 16:24 [PATCH 0/4] Add I2C controller support for MT6797 SoC Manivannan Sadhasivam
2020-02-22 16:24 ` [PATCH 1/4] dt-bindings: i2c: Document I2C controller binding " Manivannan Sadhasivam
2020-02-26 22:23 ` Rob Herring
2020-05-15 14:48 ` Matthias Brugger [this message]
2020-05-15 16:56 ` Wolfram Sang
2020-05-16 15:05 ` Matthias Brugger
2020-02-22 16:24 ` [PATCH 2/4] arm64: dts: mediatek: Add I2C support " Manivannan Sadhasivam
2020-02-22 16:24 ` [PATCH 3/4] arm64: dts: mediatek: Enable I2C support for 96Boards X20 Development board Manivannan Sadhasivam
2020-02-22 16:24 ` [PATCH 4/4] arm64: dts: mediatek: Switch to SPDX license identifier for MT6797 SoC Manivannan Sadhasivam
2020-05-12 14:12 ` [PATCH 0/4] Add I2C controller support " Manivannan Sadhasivam
2020-05-16 15:05 ` Matthias Brugger
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=aa9ea456-dbee-229c-aea0-4860c6eb7adf@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=adamboardman@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=wsa@the-dreams.de \
/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).