From: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
To: Mike Turquette <mturquette@ti.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Rob Herring <rob.herring@calxeda.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] CLK: clk-twl6040: Initial clock driver for OMAP4+ McPDM fclk clock
Date: Tue, 30 Oct 2012 08:39:25 +0100 [thread overview]
Message-ID: <508F842D.8000407@ti.com> (raw)
In-Reply-To: <20121029173008.18780.35000@nucleus>
Hi Mike,
On 10/29/2012 06:30 PM, Mike Turquette wrote:
> Peter,
>
> The patch looks good to me. To be clear, you wan this to go through
> clk-next or the mfd tree for avoiding conflicts?
clk-next is the best place for it I think. The MFD part to register the device
can still wait till we have ccf support on OMAP4.
Thank you,
Péter
next prev parent reply other threads:[~2012-10-30 7:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 14:30 [PATCH] CLK: clk-twl6040: Initial clock driver for OMAP4+ McPDM fclk clock Peter Ujfalusi
2012-10-29 17:30 ` Mike Turquette
2012-10-30 7:39 ` Péter Ujfalusi [this message]
2012-10-30 10:05 ` Mike Turquette
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=508F842D.8000407@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=arnd@arndb.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@ti.com \
--cc=rob.herring@calxeda.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