LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ray Jui <ray.jui@broadcom.com>
To: Rob Herring <robh@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Pramod Kumar <pramod.kumar@broadcom.com>
Subject: Re: [PATCH 2/3] clk: bcm: Update and add tingray clock entries
Date: Fri, 1 Jun 2018 10:56:27 -0700 [thread overview]
Message-ID: <a354f3d1-051d-8b68-e6b3-ce7a739c10c9@broadcom.com> (raw)
In-Reply-To: <20180531162556.GA955@rob-hp-laptop>
Hi Rob,
On 5/31/2018 9:25 AM, Rob Herring wrote:
> On Fri, May 25, 2018 at 09:45:16AM -0700, Ray Jui wrote:
>> Update and add Stingray clock definitions and tables so they match the
>> binding document and the latest ASIC datasheet
>>
>> Signed-off-by: Pramod Kumar <pramod.kumar@broadcom.com>
>> Signed-off-by: Ray Jui <ray.jui@broadcom.com>
>> ---
>> drivers/clk/bcm/clk-sr.c | 135 ++++++++++++++++++++++++++++++++-----
>> include/dt-bindings/clock/bcm-sr.h | 24 +++++--
>
> This goes in the 1st patch.
Please help to confirm. You want 1st patch and 2nd patch to be combined
into a single patch?
Thanks.
>
>> 2 files changed, 137 insertions(+), 22 deletions(-)
next prev parent reply other threads:[~2018-06-01 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 16:45 [PATCH 0/3] Update Broadcom Stingray " Ray Jui
2018-05-25 16:45 ` [PATCH 1/3] dt-bindings: clk: Update Stingray binding doc Ray Jui
2018-05-25 16:45 ` [PATCH 2/3] clk: bcm: Update and add tingray clock entries Ray Jui
2018-05-30 23:41 ` Stephen Boyd
2018-05-31 0:23 ` Ray Jui
2018-05-31 16:25 ` Rob Herring
2018-06-01 17:56 ` Ray Jui [this message]
2018-06-01 19:02 ` Rob Herring
2018-06-02 0:47 ` Ray Jui
2018-05-25 16:45 ` [PATCH 3/3] arm64: dts: Update Stingray clock DT nodes Ray Jui
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=a354f3d1-051d-8b68-e6b3-ce7a739c10c9@broadcom.com \
--to=ray.jui@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=pramod.kumar@broadcom.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--subject='Re: [PATCH 2/3] clk: bcm: Update and add tingray clock entries' \
/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
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).