linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] clk fixes for v4.20-rc1
Date: Sat, 10 Nov 2018 10:04:23 -0800	[thread overview]
Message-ID: <20181110180423.208899-1-sboyd@kernel.org> (raw)

The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:

  Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixes-for-linus

for you to fetch changes up to 1aefa98b010e9cc7a07046cbcb1237ddad85b708:

  clk: qcom: gcc: Fix board clock node name (2018-11-09 14:13:55 -0800)

----------------------------------------------------------------
A small set of fixes for clk drivers. One to fix a DT refcount
imbalance, two to mark some Amlogic clks as critical, and one final
one that fixes a clk name for the Qualcomm driver merged this cycle.

----------------------------------------------------------------
Christian Hewitt (1):
      clk: meson-gxbb: set fclk_div3 as CLK_IS_CRITICAL

Jerome Brunet (1):
      clk: meson: axg: mark fdiv2 and fdiv3 as critical

Ricardo Ribalda Delgado (1):
      clk: fixed-factor: fix of_node_get-put imbalance

Vinod Koul (1):
      clk: qcom: gcc: Fix board clock node name

 drivers/clk/clk-fixed-factor.c |  1 +
 drivers/clk/meson/axg.c        | 13 +++++++++++++
 drivers/clk/meson/gxbb.c       | 12 ++++++++++++
 drivers/clk/qcom/gcc-qcs404.c  |  2 +-
 4 files changed, 27 insertions(+), 1 deletion(-)

-- 
Sent by a computer through tubes

             reply	other threads:[~2018-11-10 18:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-10 18:04 Stephen Boyd [this message]
2018-11-10 19:35 ` [GIT PULL] clk fixes for v4.20-rc1 pr-tracker-bot
2018-11-14  0:55 ` pr-tracker-bot

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=20181110180423.208899-1-sboyd@kernel.org \
    --to=sboyd@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=torvalds@linux-foundation.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).