From: Jun Sun <jsun@mvista.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Jeff Baitis <baitisj@evolution.com>,
Pete Popov <ppopov@mvista.com>,
linux-mips@linux-mips.org, Matthew Dharm <mdharm@momenco.com>,
jsun@mvista.com
Subject: Re: Improperly handled case in arch/mips/au1000/common/time.c
Date: Tue, 22 Apr 2003 16:13:38 -0700 [thread overview]
Message-ID: <20030422161338.H28544@mvista.com> (raw)
In-Reply-To: <20030423010727.A8410@linux-mips.org>; from ralf@linux-mips.org on Wed, Apr 23, 2003 at 01:07:27AM +0200
On Wed, Apr 23, 2003 at 01:07:27AM +0200, Ralf Baechle wrote:
> On Tue, Apr 22, 2003 at 03:56:25PM -0700, Jun Sun wrote:
>
> > I think this is a good example to show benefit of code sharing.
> > There is no good reason for au1x00 boards of not using new time.c.
> > You get to write less board code, fewer bugs and future proof.
>
> There are just three configurations left using CONFIG_OLD_TIME_C:
>
> - EV64120 which I guess can be considered abandonded
> - Momenco Ocelot (Matthew, feel like you have time to take care of
> this?)
> - RM200 (semi-maintained, my turn to fix it ...)
>
> Seems like it's time to get rid of CONFIG_OLD_TIME_C.
>
If we were going to get rid of CONFIG_OLD_TIME_C, I propose
to make CONFIG_NEW_TIME_C as the default and therefore removed as well.
And make other boards using private time_init() functions to use
CONFIG_HAVE_PRIVATE_TIME.
... in the spirit of encouraging code sharing. :)
Jun
next prev parent reply other threads:[~2003-04-22 23:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 19:54 Improperly handled case in arch/mips/au1000/common/time.c Jeff Baitis
2003-04-22 20:20 ` Pete Popov
2003-04-22 20:49 ` Ralf Baechle
2003-04-22 22:56 ` Jun Sun
2003-04-22 23:00 ` Pete Popov
2003-04-22 23:07 ` Jun Sun
2003-04-23 15:35 ` Dan Malek
2003-04-22 23:07 ` Ralf Baechle
2003-04-22 23:13 ` Jun Sun [this message]
2003-04-22 23:18 ` Pete Popov
2003-04-22 23:30 ` Jun Sun
2003-04-23 0:29 ` Ralf Baechle
2003-04-23 13:24 ` Maciej W. Rozycki
2003-04-22 23:17 ` Matthew Dharm
2003-04-22 23:17 ` Matthew Dharm
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=20030422161338.H28544@mvista.com \
--to=jsun@mvista.com \
--cc=baitisj@evolution.com \
--cc=linux-mips@linux-mips.org \
--cc=mdharm@momenco.com \
--cc=ppopov@mvista.com \
--cc=ralf@linux-mips.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 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.