From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 00/15] clk: ti: cleanups for 4.12 merge window
Date: Sat, 11 Mar 2017 14:49:51 +0200 [thread overview]
Message-ID: <1489236606-24023-1-git-send-email-t-kristo@ti.com> (raw)
Hi,
This series is basically just a rebase of v1 of the same, with Tony's
acks added.
https://www.spinics.net/lists/arm-kernel/msg562362.html
Boot tested on the omap2+ boards I have access to, no issues seen caused
by this series.
am335x-evm : boot ok
am335x-evmsk : boot ok
am37x-evm : boot ok
am437x-sk : boot ok
am437x-gp-evm : boot ok
am57xx-evm : boot ok
omap3-beagle-xm : boot ok
omap3-beagle : boot ok
am335x-boneblack: boot ok
am335x-bone : boot ok
dra72x-evm : BOOT FAIL! (farm issue, failed to mount NFS rootfs)
dra7xx-evm : boot ok
ldp3430 : BOOT FAIL! (farm issue, bootloader ethernet failure)
omap3-n900 : boot ok
omap5-uevm : boot ok
omap4-panda-es : boot ok
omap4-panda : boot ok
omap2430-sdp : boot ok
omap3430-sdp : boot ok
omap4-sdp-es23plus: boot ok
Branch available on top of 4.11-rc1 here:
tree: https://github.com/t-kristo/linux-pm.git
branch: for-4.12-ti-clk-cleanups
-Tero
next reply other threads:[~2017-03-11 12:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 12:49 Tero Kristo [this message]
2017-03-11 12:49 ` [PATCHv2 01/15] clk: ti: remove un-used definitions from public clk_hw_omap struct Tero Kristo
2017-03-11 12:49 ` [PATCHv2 02/15] clk: ti: add support for automatic clock alias generation Tero Kristo
2017-03-11 12:49 ` [PATCHv2 03/15] clk: ti: add API for creating aliases automatically for simple clock types Tero Kristo
2017-03-11 12:49 ` [PATCHv2 04/15] clk: ti: use automatic clock alias generation framework Tero Kristo
2017-03-11 12:49 ` [PATCHv2 05/15] clk: ti: add clkdm_lookup to the exported functions Tero Kristo
2017-03-11 12:49 ` [PATCHv2 06/15] clk: ti: move omap2_init_clk_clkdm under TI clock driver Tero Kristo
2017-03-11 12:49 ` [PATCHv2 07/15] clk: ti: enforce const types on string arrays Tero Kristo
2017-03-11 12:49 ` [PATCHv2 08/15] clk: ti: omap4: cleanup unnecessary clock aliases Tero Kristo
2017-03-11 12:50 ` [PATCHv2 09/15] clk: ti: drop unnecessary MEMMAP_ADDRESSING flag Tero Kristo
2017-03-11 12:50 ` [PATCHv2 10/15] clk: ti: mux: convert TI mux clock to use its internal data representation Tero Kristo
2017-03-11 12:50 ` [PATCHv2 11/15] clk: ti: divider: convert TI divider clock to use its own " Tero Kristo
2017-03-11 12:50 ` [PATCHv2 12/15] clk: ti: divider: add driver internal API for parsing divider data Tero Kristo
2017-03-11 12:50 ` [PATCHv2 13/15] clk: ti: gate: export gate_clk_ops locally Tero Kristo
2017-03-11 12:50 ` [PATCHv2 14/15] clk: ti: dpll44xx: fix clksel register initialization Tero Kristo
2017-03-11 12:50 ` [PATCHv2 15/15] clk: ti: convert to use proper register definition for all accesses Tero Kristo
2018-01-17 13:27 ` Adam Ford
2018-01-17 14:02 ` Tero Kristo
2018-01-17 15:15 ` Adam Ford
2018-01-17 15:33 ` Adam Ford
2018-01-17 21:19 ` Tony Lindgren
2018-01-17 21:44 ` Adam Ford
2018-01-18 7:34 ` Tero Kristo
2018-01-18 13:26 ` Adam Ford
2018-01-18 13:29 ` Tero Kristo
2018-01-18 14:12 ` Adam Ford
2018-01-19 9:42 ` Tero Kristo
2018-01-19 16:43 ` Adam Ford
2018-01-22 7:07 ` Tero Kristo
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=1489236606-24023-1-git-send-email-t-kristo@ti.com \
--to=t-kristo@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).