From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 01/10] clk: shmobile: sh73a0 common clock framework implementation
Date: Tue, 09 Sep 2014 20:46:11 +0000 [thread overview]
Message-ID: <4800466.gxsmJrnFHZ@avalon> (raw)
In-Reply-To: <1409649186-1046-2-git-send-email-ulrich.hecht+renesas@gmail.com>
On Thursday 04 September 2014 16:13:58 Simon Horman wrote:
> On Tue, Sep 02, 2014 at 11:12:57AM +0200, Ulrich Hecht wrote:
> > Driver for the SH73A0's clocks that are too specific to be supported by a
> > generic driver.
> >
> > Signed-off-by: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
> > ---
> >
> > .../bindings/clock/renesas,sh73a0-cpg-clocks.txt | 31 ++++
> > drivers/clk/shmobile/Makefile | 1 +
> > drivers/clk/shmobile/clk-sh73a0.c | 202 ++++++++++++++++
> > 3 files changed, 234 insertions(+)
> > create mode 100644
> > Documentation/devicetree/bindings/clock/renesas,sh73a0-cpg-clocks.txt
> > create mode 100644 drivers/clk/shmobile/clk-sh73a0.c
>
> Its not a big deal to me but there seems to be some precedence
> for having separate patches for the driver and documenting its bindings.
devicetree@vger.kernel.org must be CC'ed on DT bindings patches. As a resend
is thus needed, the patch could be split.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-09-09 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 9:12 [PATCH v2 01/10] clk: shmobile: sh73a0 common clock framework implementation Ulrich Hecht
2014-09-03 5:40 ` Mike Turquette
2014-09-03 7:50 ` Ulrich Hecht
2014-09-04 6:49 ` Simon Horman
2014-09-04 7:13 ` Simon Horman
2014-09-09 20:46 ` Laurent Pinchart [this message]
2014-09-09 21:16 ` Laurent Pinchart
2014-09-09 21:24 ` Laurent Pinchart
2014-09-09 22:19 ` Mike Turquette
2014-09-09 22:27 ` Laurent Pinchart
2014-09-10 0:05 ` Simon Horman
2014-09-10 16:59 ` Mike Turquette
2014-09-12 8:50 ` Ulrich Hecht
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=4800466.gxsmJrnFHZ@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.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).