From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Allwinner clock fixes for 4.11, again
Date: Mon, 17 Apr 2017 11:33:11 -0700 [thread overview]
Message-ID: <20170417183311.GR7065@codeaurora.org> (raw)
In-Reply-To: <20170413095938.ac4zjp7ql6y76sst@lukather>
On 04/13, Maxime Ripard wrote:
> Hi Mike, Stephen,
>
> Here is another PR, without the patches that you didn't want as fixes.
>
> A few more fixes showed up in between, one of them being another build
> fix, the other one fixing random CPU crashes happening with CPUfreq
> since 4.11
>
> Please merge it for one of 4.11-rc's, thanks!
> Maxime
Thanks. Pulled into clk-fixes. I'll probably send it off in a
day or so.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2017-04-17 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 9:59 [GIT PULL] Allwinner clock fixes for 4.11, again Maxime Ripard
2017-04-17 18:33 ` Stephen Boyd [this message]
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=20170417183311.GR7065@codeaurora.org \
--to=sboyd@codeaurora.org \
--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).