From: Mark Brown <broonie@kernel.org>
To: Simon Horman <horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Magnus Damm <magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v3 2/2] spi: sh-hspi: Do not specifically request shyway_clk clock
Date: Mon, 14 Apr 2014 20:15:52 +0000 [thread overview]
Message-ID: <20140414201552.GZ25182@sirena.org.uk> (raw)
In-Reply-To: <1397439698-30123-4-git-send-email-horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
On Mon, Apr 14, 2014 at 10:41:38AM +0900, Simon Horman wrote:
> Rather than requesting the shyway_clk call clk_get with
> the device and a NULL con_id.
>
> This is in keeping with the way that clk_get() is called
> on other drivers used by Renesas Gen 1 SoCs. And I believe
> it is compatible with supplying clocks via DT, unlike the current code.
Applied, thanks.
> --
I think you were looking for --- there, though I just included
everything in the changelog anyway.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-04-14 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 1:41 [PATCH v3 0/2] spi: sh-hspi: Do not specifically request shyway_clk clock Simon Horman
[not found] ` <1397439698-30123-1-git-send-email-horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2014-04-14 1:41 ` [PATCH v3 1/2] ARM: shmobile: r8a7778: Use clks as MSTP007 parent Simon Horman
2014-04-14 9:27 ` Laurent Pinchart
2014-04-14 20:14 ` Mark Brown
2014-04-14 1:41 ` [PATCH v2 repost 1/2] ARM: shmobile: r8a7779: " Simon Horman
[not found] ` <1397439698-30123-3-git-send-email-horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2014-04-14 1:59 ` Simon Horman
2014-04-14 1:41 ` [PATCH v3 2/2] spi: sh-hspi: Do not specifically request shyway_clk clock Simon Horman
[not found] ` <1397439698-30123-4-git-send-email-horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2014-04-14 20:15 ` Mark Brown [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=20140414201552.GZ25182@sirena.org.uk \
--to=broonie@kernel.org \
--cc=horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org \
--cc=linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).