All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: J William Piggott <elseifthen@gmx.com>
Cc: Karel Zak <kzak@redhat.com>, util-linux <util-linux@vger.kernel.org>
Subject: Re: RFC hwclock: refactoring
Date: Mon, 16 Feb 2015 07:32:52 -0500	[thread overview]
Message-ID: <20150216123252.GE4359@vapier> (raw)
In-Reply-To: <54E1D668.3070001@gmx.com>

[-- Attachment #1: Type: text/plain, Size: 861 bytes --]

On 16 Feb 2015 06:37, J William Piggott wrote:
> On 02/16/2015 04:02 AM, Mike Frysinger wrote:
> > On 23 Nov 2014 13:31, Sami Kerola wrote:
> >> On 22 November 2014 at 21:20, JWP wrote:
> >>> 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.
> > 
> > Gentoo still produces up-to-date releases
> 
> Yes, I contacted the two most authoritative Alpha people I could find,
> Tobias Klausmann and Matt Turner. Matt requested that we continue to
> maintain hwclock's Alpha code. I forgot to post a follow up here about
> it, sorry.

no worries.  if people are interested in refactoring code and want to verify 
alpha works (and qemu-system isn't doing it for them), we can get you access 
to real alpha hardware :).
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-02-16 12:32 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
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 [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=20150216123252.GE4359@vapier \
    --to=vapier@gentoo.org \
    --cc=elseifthen@gmx.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.