From: Bob Tracy <rct@gherkin.frus.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Richard Henderson <rth@twiddle.net>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Matt Turner <mattst88@gmail.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-alpha@vger.kernel.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: is alpha jensen support dead?
Date: Sun, 21 May 2017 13:11:28 -0500 [thread overview]
Message-ID: <20170521181128.GA13376@gherkin.frus.com> (raw)
In-Reply-To: <20170521085848.GA14559@lst.de>
On Sun, May 21, 2017 at 10:58:48AM +0200, Christoph Hellwig wrote:
> Btw, how well is alpha working these days? It looks like there hasn't
> been any maintainer activity for about two years.
Speaking for myself, the PWS 433au I've got continues to function
admirably as my IPv6 gateway. Debian unstable and experimental updates
continue to apply and work within the limits of my ability to test them.
I'm building and running the release candidates and final versions of
the kernel.org tree with the unstable tool chain. Recently there was a
FTBFS due to relocation issues during the final vmlinux link on alpha:
that has been fixed, and what's left of the alpha community is pretty
quick to respond and identify what's going on.
In summary, alpha is still a viable platform for *me*.
--Bob
next prev parent reply other threads:[~2017-05-21 18:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 8:58 Christoph Hellwig
2017-05-21 18:11 ` Bob Tracy [this message]
2017-05-22 7:51 ` Christoph Hellwig
2017-06-05 12:49 ` Maciej W. Rozycki
2017-05-22 5:33 ` Matt Turner
2017-05-22 5:50 ` Michael Ellerman
2017-05-24 9:16 ` Christian Borntraeger
2017-05-24 9:30 ` Christoph Hellwig
[not found] <20170521105032.5F0807FF0E@ilves.cyber.ee>
2017-05-21 11:18 ` Meelis Roos
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=20170521181128.GA13376@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=borntraeger@de.ibm.com \
--cc=hch@lst.de \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=rth@twiddle.net \
/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
all inboxes | Powered by JetHome®