From: Tony Lindgren <tony@atomide.com>
To: Faiz Abbas <faiz_abbas@ti.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-clk@vger.kernel.org, robh+dt@kernel.org,
bcousson@baylibre.com, paul@pwsan.com, t-kristo@ti.com,
mark.rutland@arm.com, sboyd@kernel.org
Subject: Re: [PATCH v5 2/6] clk: ti: dra7: Add clkctrl clock data for the mcan clocks
Date: Mon, 9 Jul 2018 22:44:38 -0700 [thread overview]
Message-ID: <20180710054438.GE99251@atomide.com> (raw)
In-Reply-To: <20180709164841.14182-3-faiz_abbas@ti.com>
* Faiz Abbas <faiz_abbas@ti.com> [180709 16:50]:
> Add clkctrl data for the m_can clocks and register it within the
> clkctrl driver
I'll apply patches 2 to 5 to omap-for-v4.19/ti-sysc. The clock
patch is trivial enough to not have to wait for Tero to be back
online.
And I'll apply the dts changes into omap-for-v4.19/dt-mcan based
on omap-for-v4.19/ti-sysc because of the dependency to the clocks.
Regards,
Tony
next prev parent reply other threads:[~2018-07-10 5:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 16:48 [PATCH v5 0/6] Add MCAN Support for dra76x Faiz Abbas
2018-07-09 16:48 ` [PATCH v5 1/6] ARM: dts: dra762: Add MCAN clock support Faiz Abbas
2018-07-09 16:48 ` [PATCH v5 2/6] clk: ti: dra7: Add clkctrl clock data for the mcan clocks Faiz Abbas
2018-07-10 5:44 ` Tony Lindgren [this message]
2018-07-09 16:48 ` [PATCH v5 3/6] bus: ti-sysc: Add support for using ti-sysc for MCAN on dra76x Faiz Abbas
2018-07-09 16:48 ` [PATCH v5 4/6] bus: ti-sysc: Add support for software reset Faiz Abbas
2018-07-10 11:42 ` Tony Lindgren
2018-07-10 13:20 ` Faiz Abbas
2018-07-09 16:48 ` [PATCH v5 5/6] ARM: dts: Add generic interconnect target module node for MCAN Faiz Abbas
2018-07-09 16:48 ` [PATCH v5 6/6] ARM: dts: dra76x: Add MCAN node Faiz Abbas
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=20180710054438.GE99251@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=faiz_abbas@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=paul@pwsan.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).