From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Stephen Warren <swarren@nvidia.com>,
treding@nvidia.com, Sasha Levin <sashal@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
linux- stable <stable@vger.kernel.org>,
lkft-triage@lists.linaro.org
Subject: Re: clk: tegra: Mark fuse clock as critical - build failed on 4.4-stable tree
Date: Mon, 10 Feb 2020 04:25:27 -0800 [thread overview]
Message-ID: <20200210122527.GB413013@kroah.com> (raw)
In-Reply-To: <CA+G9fYt1d+kyNkqzaSMO2D9X4EbmU6dq+Qaw2VC_2B7xxdb3Jg@mail.gmail.com>
On Mon, Feb 10, 2020 at 11:49:52AM +0530, Naresh Kamboju wrote:
> This patch caused build failed on stable rc 4.4 branch for arm64
> Juno-r2 device and arm beagleboard x15 device
>
> commit bf83b96f87ae2abb1e535306ea53608e8de5dfbb upstream.
THanks for letting me know, I've now dropped it from the tree.
greg k-h
prev parent reply other threads:[~2020-02-10 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 6:19 clk: tegra: Mark fuse clock as critical - build failed on 4.4-stable tree Naresh Kamboju
2020-02-10 12:25 ` Greg Kroah-Hartman [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=20200210122527.GB413013@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=swarren@nvidia.com \
--cc=treding@nvidia.com \
/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).