All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sami Kerola <kerolasa@iki.fi>
To: JWP <elseifthen@gmx.com>
Cc: Karel Zak <kzak@redhat.com>, util-linux <util-linux@vger.kernel.org>
Subject: Re: RFC hwclock: refactoring
Date: Sun, 23 Nov 2014 13:31:03 +0000	[thread overview]
Message-ID: <CAG27Bk3zu-8Qar_k44uM3_8_kOddJkqvb1be1_KmjkBGfBGcYA@mail.gmail.com> (raw)
In-Reply-To: <5470FE32.9030805@gmx.com>

On 22 November 2014 at 21:20, JWP <elseifthen@gmx.com> wrote:
> So, I noticed when *fdisk were rewritten that some antiquated
> code was dropped.  I would like some opinions on whether this
> should be done when refactoring hwclock.
>
> For example, do we need a workaround for the 1994 Award BIOS
> bug?

I agree with Benno, it is time to say goodbye to that code.

> Do we need Alpha code?  Is there a Linux distro that
> still officially supports Alpha machines?

I'm not sure if there is any up to date distribution for Alpha. Kernel
crew seems to still care alpha, so it is not completely dead.

http://marc.info/?t=140518903000002&r=1&w=2

Maybe the question should be rephrased. How about dropping the Alpha
cmos support? It looks like Alpha has rtc support.

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/alpha/kernel/rtc.c

> Any other ideas regarding this topic are welcome.

Removal of i386 references should be safe.

http://news.softpedia.com/news/Linux-Kernel-3-8-Says-Goodbye-to-i386-314293.shtml

Since there is no other than Alpha & i386 references to cmos code, all
of it is subject for removal.

-- 
Sami Kerola
http://www.iki.fi/kerolasa/

  parent reply	other threads:[~2014-11-23 13:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-22 21:20 RFC hwclock: refactoring JWP
2014-11-23 10:27 ` Benno Schulenberg
2014-11-24  1:56   ` JWP
2014-11-23 13:31 ` Sami Kerola [this message]
2014-11-23 15:32   ` Sami Kerola
2014-11-24  1:54     ` JWP
2014-11-24 10:14       ` Karel Zak
2015-02-16  9:02   ` Mike Frysinger
2015-02-16 11:37     ` J William Piggott
2015-02-16 12:32       ` Mike Frysinger

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=CAG27Bk3zu-8Qar_k44uM3_8_kOddJkqvb1be1_KmjkBGfBGcYA@mail.gmail.com \
    --to=kerolasa@iki.fi \
    --cc=elseifthen@gmx.com \
    --cc=kerolasa@gmail.com \
    --cc=kzak@redhat.com \
    --cc=util-linux@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 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.