Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: vagabon.xyz@gmail.com, linux-mips@linux-mips.org
Subject: Re: [PATCH 2/3] time: replace board_time_init() by plat_clk_setup()
Date: Fri, 11 May 2007 12:41:38 +0100	[thread overview]
Message-ID: <20070511114138.GH2732@linux-mips.org> (raw)
In-Reply-To: <20070506.010313.41199101.anemo@mba.ocn.ne.jp>

On Sun, May 06, 2007 at 01:03:13AM +0900, Atsushi Nemoto wrote:

> How about keeping board_time_init pointer as is and adding
> plat_clk_setup only for simple platforms?

The idea of having such function pointer is quite nice.  In theory.  In
practice it seems alot of people who are bringing up Linux on a new
platform miss those hooks.  A new mandatory platform hook that if missing
is resulting in a linker error is preferable, I think.

  Ralf

  parent reply	other threads:[~2007-05-11 11:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04 15:36 [PATCH 1/3] clocksource: use CLOCKSOURCE_MASK() macro Franck Bui-Huu
2007-05-04 15:36 ` [PATCH 2/3] time: replace board_time_init() by plat_clk_setup() Franck Bui-Huu
2007-05-04 15:36   ` [PATCH 3/3] time: implement read_persistent_clock() Franck Bui-Huu
2007-05-05 16:03   ` [PATCH 2/3] time: replace board_time_init() by plat_clk_setup() Atsushi Nemoto
2007-05-07  8:50     ` Franck Bui-Huu
2007-05-07  9:28       ` Atsushi Nemoto
2007-05-07 10:08         ` Franck Bui-Huu
2007-05-09 13:54         ` Ralf Baechle
2007-05-11 11:41     ` Ralf Baechle [this message]
2007-05-11 12:26       ` Franck Bui-Huu
2007-05-05 16:16   ` Atsushi Nemoto
2007-05-07  8:51     ` Franck Bui-Huu
2007-05-09 13:22 ` [PATCH 1/3] clocksource: use CLOCKSOURCE_MASK() macro Ralf Baechle

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=20070511114138.GH2732@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --cc=vagabon.xyz@gmail.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