public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: Felipe Balbi <felipe.lima@indt.org.br>
Cc: linux-omap@vger.kernel.org, OMAP <Linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] ARM: OMAP: MACH-OMAP1: Fix compilation issues for OMAP1
Date: Mon, 26 Nov 2007 20:51:00 +0100	[thread overview]
Message-ID: <474B23A4.7090902@googlemail.com> (raw)
In-Reply-To: <1196092220-6633-1-git-send-email-felipe.lima@indt.org.br>

Felipe Balbi wrote:
> After commit 6e0d7b9283a5b91bf2c2adc7801e426fd563bc13 building
> is broken for omap1 archs due to double definition of sched_clock().
> 
> sched_clock() has moved to plat-omap/common.c so it's ok removing it
> from mach-omap1/time.c

While trying to find this patch in list archive, I found that you sent 
it only to our new list at vger.kernel.org [1]. Nice, now I'm sure 
that mails from that list reach me as well ;) But we have no archive 
there yet. So for some time I think CC to 
Linux-omap-open-source@linux.omap.com would be good as well.

Regards

Dirk

[1] http://vger.kernel.org/vger-lists.html#linux-omap

> Signed-off-by: Felipe Balbi <felipe.lima@indt.org.br>
> ---
>  arch/arm/mach-omap1/time.c |   15 ---------------
>  1 files changed, 0 insertions(+), 15 deletions(-)
> 
> diff --git a/arch/arm/mach-omap1/time.c b/arch/arm/mach-omap1/time.c
> index a4f8b20..872b965 100644
> --- a/arch/arm/mach-omap1/time.c
> +++ b/arch/arm/mach-omap1/time.c
> @@ -262,21 +262,6 @@ static void __init omap_init_clocksource(unsigned long rate)
>  
>  
>  /*
> - * Scheduler clock - returns current time in nanosec units.
> - */
> -unsigned long long sched_clock(void)
> -{
> -	unsigned long ticks = 0 - omap_mpu_timer_read(1);
> -	unsigned long long ticks64;
> -
> -	ticks64 = omap_mpu_timer2_overflows;
> -	ticks64 <<= 32;
> -	ticks64 |= ticks;
> -
> -	return cycles_2_ns(ticks64);
> -}
> -
> -/*
>   * ---------------------------------------------------------------------------
>   * Timer initialization
>   * ---------------------------------------------------------------------------

       reply	other threads:[~2007-11-26 19:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1196092220-6633-1-git-send-email-felipe.lima@indt.org.br>
2007-11-26 19:51 ` Dirk Behme [this message]
2007-11-26 19:53   ` [PATCH] ARM: OMAP: MACH-OMAP1: Fix compilation issues for OMAP1 Felipe Balbi
2007-11-26 20:09   ` Tony Lindgren
2007-11-29 15:59     ` Switching to vger mailing list, was: " Dirk Behme
2007-11-29 17:54       ` Tony Lindgren
2007-11-29 18:14         ` Switching to vger mailing list Dirk Behme

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=474B23A4.7090902@googlemail.com \
    --to=dirk.behme@googlemail.com \
    --cc=Linux-omap-open-source@linux.omap.com \
    --cc=felipe.lima@indt.org.br \
    --cc=linux-omap@vger.kernel.org \
    /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