From: viresh kumar <viresh.linux@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, sshtylyov@mvista.com, spear-devel@list.st.com
Subject: Re: [PATCH V3 1/3] ata: pata_arasan: Add clk_{un}prepare() support
Date: Wed, 13 Jun 2012 10:12:39 +0100 [thread overview]
Message-ID: <CAOh2x==5dGi4fyk3dYwSaBVYD-jD9tLOjbLffLi=LLT808O-oA@mail.gmail.com> (raw)
In-Reply-To: <4FBBF09D.1010607@garzik.org>
Hi Jeff,
On Tue, May 22, 2012 at 9:01 PM, Jeff Garzik <jeff@garzik.org> wrote:
> On 05/09/2012 12:08 AM, Viresh Kumar wrote:
>>
>> clk_{un}prepare is mandatory for platforms using common clock framework.
>> Since
>> this driver is used by SPEAr platform, which supports common clock
>> framework,
>> add clk_{un}prepare() support for it.
>>
>> Signed-off-by: Viresh Kumar<viresh.kumar@st.com>
>> ---
>> drivers/ata/pata_arasan_cf.c | 4 ++--
>> 1 files changed, 2 insertions(+), 2 deletions(-)
>
>
>
>
> these do not apply to upstream, for me...
>
Sorry for being late. I rebased them on linux-next that time as they
had few dependency commits there.
Can you try it there?
--
Viresh
next prev parent reply other threads:[~2012-06-13 9:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 4:08 [PATCH V3 0/3] ata: pata_arasan and ahci_platform updates Viresh Kumar
2012-05-09 4:08 ` [PATCH V3 1/3] ata: pata_arasan: Add clk_{un}prepare() support Viresh Kumar
2012-05-22 20:01 ` Jeff Garzik
2012-06-13 9:12 ` viresh kumar [this message]
2012-07-16 11:37 ` viresh kumar
2012-05-09 4:09 ` [PATCH V3 2/3] ata: pata_arasan: add Device Tree probing capability Viresh Kumar
2012-05-09 4:09 ` [PATCH V3 3/3] ata/ahci_platform: Add clock framework support Viresh Kumar
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='CAOh2x==5dGi4fyk3dYwSaBVYD-jD9tLOjbLffLi=LLT808O-oA@mail.gmail.com' \
--to=viresh.linux@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=spear-devel@list.st.com \
--cc=sshtylyov@mvista.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).