From: Christoph Hellwig <hch@lst.de>
To: Bob Tracy <rct@gherkin.frus.com>
Cc: Christoph Hellwig <hch@lst.de>,
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: Mon, 22 May 2017 09:51:28 +0200 [thread overview]
Message-ID: <20170522075128.GB2081@lst.de> (raw)
In-Reply-To: <20170521181128.GA13376@gherkin.frus.com>
On Sun, May 21, 2017 at 01:11:28PM -0500, Bob Tracy wrote:
> 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*.
Great! Still makes me wonder about Jensen, which appears to be
the only platform that requires a different build than the normal
generic PCI-enabled kernel. And I suspect it's pretty much dead
at this point..
next prev parent reply other threads:[~2017-05-22 7:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 8:58 is alpha jensen support dead? Christoph Hellwig
2017-05-21 18:11 ` Bob Tracy
2017-05-21 18:11 ` Bob Tracy
2017-05-22 7:51 ` Christoph Hellwig [this message]
2017-06-05 12:49 ` Maciej W. Rozycki
2017-06-05 12:49 ` Maciej W. Rozycki
2017-05-22 5:33 ` Matt Turner
2017-05-22 5:33 ` Matt Turner
2017-05-22 5:50 ` Michael Ellerman
2017-05-22 5:50 ` Michael Ellerman
2017-05-24 9:16 ` Christian Borntraeger
2017-05-24 9:16 ` Christian Borntraeger
2017-05-24 9:30 ` Christoph Hellwig
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=20170522075128.GB2081@lst.de \
--to=hch@lst.de \
--cc=borntraeger@de.ibm.com \
--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=rct@gherkin.frus.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;
as well as URLs for NNTP newsgroup(s).