From: Tony Lindgren <tony@atomide.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Tero Kristo <t-kristo@ti.com>,
linux-clk <linux-clk@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL] clk: ti: changes for 5.6
Date: Thu, 23 Jan 2020 08:57:54 -0800 [thread overview]
Message-ID: <20200123165754.GA5885@atomide.com> (raw)
In-Reply-To: <20200122002311.405E7217F4@mail.kernel.org>
* Stephen Boyd <sboyd@kernel.org> [200122 00:24]:
> Quoting Tero Kristo (2020-01-20 23:31:27)
> > Hi Stephen,
> >
> > Please pull these TI clock changes towards v5.6. Tony, the same branch
> > (for-5.6-ti-clk) can be considered immutable towards your DTS changes if
> > you wish to sync them with this.
>
> Thanks. Pulled into clk-next
OK. I've based the pending omap4 & 5 crypto accelerator changes on
Tero's branch and pushed out omap-for-v5.6/ti-sysc-omap45-rng. Might
be too late for v5.6, but we'll see.
Thanks,
Tony
prev parent reply other threads:[~2020-01-23 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 7:31 [GIT PULL] clk: ti: changes for 5.6 Tero Kristo
[not found] ` <20200122002311.405E7217F4@mail.kernel.org>
2020-01-23 16:57 ` Tony Lindgren [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=20200123165754.GA5885@atomide.com \
--to=tony@atomide.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=t-kristo@ti.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