From: Tali Perry <tali.perry1@gmail.com>
To: brendanhiggins@google.com, robh+dt@kernel.org,
mark.rutland@arm.com, linux@armlinux.org.uk,
avifishman70@gmail.com, tmaimon77@gmail.com, raltherr@google.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, openbmc@lists.ozlabs.org,
Tali Perry <tali.perry1@gmail.com>
Subject: [PATCH v2 0/1] *clk: npcm750: add clock header to patch, fix typos and content in dt-binding txt
Date: Thu, 15 Feb 2018 15:39:18 +0200 [thread overview]
Message-ID: <1518701959-22899-1-git-send-email-tali.perry1@gmail.com> (raw)
Add Nuvoton BMC NPCM7xx clock driver.
Nuvoton BMC NPCM7xx contain integrated clock controller which
generates and supplies clock to all modules within the NPCM7xx BMC
1 ==> 2
This patch includes fix request described here:
https://lkml.org/lkml/2018/2/8/739
(add clock header to patch, fix typos and content in dt-binding txt)
Signed-off-by: Tali Perry <tali.perry1@gmail.com>
Tali Perry (1):
clk: npcm750: update text with fixed clocks
.../bindings/clock/nuvoton,npcm750-clk.txt | 103 +++++++++++++++++++++
include/dt-bindings/clock/nuvoton,npcm7xx-clock.h | 51 ++++++++++
2 files changed, 154 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/nuvoton,npcm750-clk.txt
create mode 100644 include/dt-bindings/clock/nuvoton,npcm7xx-clock.h
--
2.14.1
next reply other threads:[~2018-02-15 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 13:39 Tali Perry [this message]
[not found] ` <1518701959-22899-1-git-send-email-tali.perry1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-15 13:39 ` [PATCH v2 1/1] clk: npcm750: update text with fixed clocks Tali Perry
[not found] ` <1518701959-22899-2-git-send-email-tali.perry1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-15 22:38 ` Brendan Higgins
2018-02-19 14:49 ` Rob Herring
2018-02-21 4:47 ` Brendan Higgins
2018-02-21 13:23 ` Rob Herring
2018-02-21 18:22 ` Brendan Higgins
2018-02-19 14:56 ` Rob Herring
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=1518701959-22899-1-git-send-email-tali.perry1@gmail.com \
--to=tali.perry1@gmail.com \
--cc=avifishman70@gmail.com \
--cc=brendanhiggins@google.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=raltherr@google.com \
--cc=robh+dt@kernel.org \
--cc=tmaimon77@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).