From: Greg KH <gregkh@linuxfoundation.org>
To: Jakob Unterwurzacher <jakob.unterwurzacher@theobroma-systems.com>
Cc: stable@vger.kernel.org, klaus.goger@theobroma-systems.com
Subject: Re: Cherry-pick "arm64: dts: rockchip: remove vdd_log from rk3399-puma" for 4.14.y?
Date: Fri, 27 Apr 2018 12:27:05 +0200 [thread overview]
Message-ID: <20180427102705.GA14567@kroah.com> (raw)
In-Reply-To: <eefb686b-37c9-612b-6494-27d009fcc782@theobroma-systems.com>
On Fri, Apr 27, 2018 at 12:13:44PM +0200, Jakob Unterwurzacher wrote:
> Dear Greg,
>
> a fix for a voltage instability on our rk3399-puma board went into 4.15
> (commit 87eba0716011, quoted below). As we have users who prefer to stay on
> longterm 4.14, would you consider cherry-picking the commit into 4.14.y? It
> applies cleanly and has no effect outside of our rk3399-puma board, where it
> fixes the instability.
Sure, now queued up, thanks.
greg k-h
prev parent reply other threads:[~2018-04-27 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 10:13 Cherry-pick "arm64: dts: rockchip: remove vdd_log from rk3399-puma" for 4.14.y? Jakob Unterwurzacher
2018-04-27 10:27 ` Greg KH [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=20180427102705.GA14567@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jakob.unterwurzacher@theobroma-systems.com \
--cc=klaus.goger@theobroma-systems.com \
--cc=stable@vger.kernel.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).