From: Wolfram Sang <wsa@the-dreams.de>
To: Gareth Williams <gareth.williams.jx@renesas.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
devicetree@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Phil Edworthy <phil.edworthy@renesas.com>
Subject: Re: [PATCH v4 0/2] i2c: designware: Add support for a bus clock
Date: Sat, 23 Feb 2019 10:32:07 +0100 [thread overview]
Message-ID: <20190223093207.GC1018@kunai> (raw)
In-Reply-To: <1550765459-14519-1-git-send-email-gareth.williams.jx@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
On Thu, Feb 21, 2019 at 04:10:57PM +0000, Gareth Williams wrote:
> The Synopsys I2C Controller has a peripheral clock that some SoCs
> require to access the registers. This series also details the new clock
> property in the bindings documentation.
Your SoB is missing for patch 1. And besides my ack, I'd still like some
feedback from the actual driver maintainers.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-23 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 16:10 [PATCH v4 0/2] i2c: designware: Add support for a bus clock Gareth Williams
2019-02-21 16:10 ` [PATCH v4 1/2] dt: snps,designware-i2c: Add clock bindings documentation Gareth Williams
2019-02-22 15:06 ` Rob Herring
2019-02-26 14:54 ` Jarkko Nikula
2019-02-26 15:39 ` Wolfram Sang
2019-02-27 7:10 ` Jarkko Nikula
2019-02-27 9:43 ` Luis de Oliveira
2019-02-26 18:39 ` Luis de Oliveira
2019-02-23 9:32 ` Wolfram Sang [this message]
2019-02-25 9:28 ` [PATCH v4 0/2] i2c: designware: Add support for a bus clock Gareth Williams
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=20190223093207.GC1018@kunai \
--to=wsa@the-dreams.de \
--cc=alexandre.belloni@bootlin.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=gareth.williams.jx@renesas.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=phil.edworthy@renesas.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).