From: "Pali Rohár" <pali.rohar@gmail.com>
To: Omar Ramirez Luna <omar.ramirez@copitl.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
Tony Lindgren <tony@atomide.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Joni Lapilainen <joni.lapilainen@gmail.com>
Subject: Re: [PATCH] tidspbridge: Fix compilation
Date: Wed, 6 Mar 2013 15:11:09 +0100 [thread overview]
Message-ID: <201303061511.09943@pali> (raw)
In-Reply-To: <CAJ6Av5O9n99t01-+dprqOkC7Nyp8vpBQANWbgZqWiemUy8Q0tQ@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1168 bytes --]
On Monday 04 March 2013 10:14:31 Omar Ramirez Luna wrote:
> Hi,
>
> On Thu, Feb 28, 2013 at 11:51 AM, Pali Rohár
<pali.rohar@gmail.com> wrote:
> > Fix includes and use
> > clk_prepare_enable/clk_disable_unprepare
> >
> > Signed-off-by: Pali Rohár <pali.rohar@gmail.com>
> > Signed-off-by: Joni Lapilainen <joni.lapilainen@gmail.com>
> > ---
> >
> > drivers/staging/tidspbridge/core/dsp-clock.c | 16
> > ++++++++--------
> > drivers/staging/tidspbridge/core/tiomap3430.c | 2 ++
> > drivers/staging/tidspbridge/core/tiomap_io.c | 2 ++
> > drivers/staging/tidspbridge/core/wdt.c | 8
> > ++++---- 4 files changed, 16 insertions(+), 12
> > deletions(-)
>
> AFAIK, this has been taken care in the past by:
>
> e16a922a staging: tidspbridge: use prepare/unprepare on dsp
> clocks fe025085 staging: tidspbridge: Fix build breakage due
> to splitting CM functions
>
> Would you mind pointing the target for your patches? Perhaps
> stable?
>
> Cheers,
>
> Omar
I was not able to compile tidspbridge on 3.8-rc3. But now with
3.8 it is fixed. So drop this patch.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-03-06 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 17:51 [PATCH] tidspbridge: Fix compilation Pali Rohár
2013-02-28 19:08 ` Greg Kroah-Hartman
2013-03-04 9:14 ` Omar Ramirez Luna
2013-03-06 14:11 ` Pali Rohár [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=201303061511.09943@pali \
--to=pali.rohar@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joni.lapilainen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omar.ramirez@copitl.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.