linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@kernel.org
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Stephen Boyd <sboyd@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] clk fixes for v4.17-rc5
Date: Fri, 18 May 2018 16:02:09 -0700	[thread overview]
Message-ID: <20180518230209.260757-1-sboyd@kernel.org> (raw)

From: Stephen Boyd <sboyd@kernel.org>

The following changes since commit c964cfc612b59910593fa10ee1c2673db274c9c7:

  Merge tag 'meson-clk-fixes-4.17-1' of https://github.com/BayLibre/clk-meson into clk-fixes (2018-05-01 14:44:16 -0700)

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 9a160601f3fb6ffa196b87d1b5643646be486405:

  clk: stm32: fix: stm32 clock drivers are not compiled by default (2018-05-15 15:47:03 -0700)

----------------------------------------------------------------
A modified revert of a patch that made new choices come out for a couple
stm32 clk drivers that really always need to be there when that
particular machine is compiled in and boot fix on i.MX for Stefan who
noticed odd behavior from the critical flag patch that came in during
the merge window.

----------------------------------------------------------------
Gabriel Fernandez (1):
      clk: stm32: fix: stm32 clock drivers are not compiled by default

Stefan Agner (1):
      clk: imx6ull: use OSC clock during AXI rate change

 drivers/clk/Kconfig          | 6 ++----
 drivers/clk/imx/clk-imx6ul.c | 2 +-
 2 files changed, 3 insertions(+), 5 deletions(-)

-- 
Sent by a computer through tubes

                 reply	other threads:[~2018-05-18 23:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180518230209.260757-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).