From: Greg KH <greg@kroah.com>
To: Adam Ford <aford173@gmail.com>
Cc: stable@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Richard Watts <rrw@kynesim.co.uk>,
Ladislav Michl <ladis@linux-mips.org>,
Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: clk: ti: omap36xx: Work around sprz319 advisory 2.1
Date: Wed, 4 Jan 2017 10:34:30 +0100 [thread overview]
Message-ID: <20170104093430.GD31677@kroah.com> (raw)
In-Reply-To: <CAHCN7xJcuq_PmNDZfeL0L8bQ3ukhQGwGN6WTu0KYbRhk3FoTUA@mail.gmail.com>
On Tue, Jan 03, 2017 at 03:41:14PM -0600, Adam Ford wrote:
> Commit 035cd485a47dda64f25ccf8a90b11a07d0b7aa7a addresses and errata
> for the clock mechanism on OMAP3630. I have tested this on Linux
> 4.4.39 and it appears to work.
>
> I would like to request this to be applied to the 4.4, 4.8, and 4.9 branches.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2017-01-04 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 21:41 clk: ti: omap36xx: Work around sprz319 advisory 2.1 Adam Ford
2017-01-04 9:34 ` 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=20170104093430.GD31677@kroah.com \
--to=greg@kroah.com \
--cc=aford173@gmail.com \
--cc=ladis@linux-mips.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=rrw@kynesim.co.uk \
--cc=sboyd@codeaurora.org \
--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).