From: Stephen Boyd <sboyd@kernel.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>,
andrew@lunn.ch, gregory.clement@bootlin.com,
jason@lakedaemon.net, linus.walleij@linaro.org,
linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
mturquette@baylibre.com, robh+dt@kernel.org,
sebastian.hesselbarth@gmail.com
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: Re: [PATCH v2 4/4] clk: kirkwood: Add support for MV98DX1135
Date: Tue, 25 Jun 2019 14:35:47 -0700 [thread overview]
Message-ID: <20190625213548.785BF2085A@mail.kernel.org> (raw)
In-Reply-To: <20190617215458.32688-5-chris.packham@alliedtelesis.co.nz>
Quoting Chris Packham (2019-06-17 14:54:58)
> The 98DX1135 is a switch chip with an integrated CPU. This is similar to
> the 98DX4122 except that the core clock speed is fixed to 166Mhz.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> ---
Applied to clk-next
prev parent reply other threads:[~2019-06-25 21:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 21:54 [PATCH v2 0/4] Add support for Marvell 98DX1135 Chris Packham
2019-06-17 21:54 ` [PATCH v2 1/4] dt-bindings: pinctrl: mvebu: Document bindings for 98DX1135 Chris Packham
2019-06-25 12:25 ` Linus Walleij
2019-06-17 21:54 ` [PATCH v2 2/4] dt-bindings: clock: mvebu: Add compatible string for 98dx1135 core clock Chris Packham
2019-06-17 22:18 ` Andrew Lunn
2019-06-25 21:35 ` Stephen Boyd
2019-06-17 21:54 ` [PATCH v2 3/4] pinctrl: mvebu: Add support for MV98DX1135 Chris Packham
2019-06-25 12:26 ` Linus Walleij
2019-06-25 20:30 ` Chris Packham
2019-06-17 21:54 ` [PATCH v2 4/4] clk: kirkwood: " Chris Packham
2019-06-25 21:35 ` Stephen Boyd [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=20190625213548.785BF2085A@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.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).