From: Christoph Hellwig <hch@lst.de>
To: Richard Henderson <rth@twiddle.net>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Matt Turner <mattst88@gmail.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
linux-alpha@vger.kernel.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: is alpha jensen support dead?
Date: Sun, 21 May 2017 10:58:48 +0200 [thread overview]
Message-ID: <20170521085848.GA14559@lst.de> (raw)
Hi all,
it seems like the Alpha Jense build (the only one using pci-noop.c)
and thus being a different build than all the later PCI capable
system has been broken since at least:
commit 6aca0503847f6329460b15b3ab2b0e30bb752793
Author: Christian Borntraeger <borntraeger@de.ibm.com>
Date: Tue Feb 2 21:46:33 2016 -0800
alpha/dma: use common noop dma ops
which switches pci-noop.c to use generic code, but fat fingered a symbol
and didn't wire up the Kconfig.
Is there any value in keeping it alive? Especially as there probably
isn't any build coverage..
Btw, how well is alpha working these days? It looks like there hasn't
been any maintainer activity for about two years.
next reply other threads:[~2017-05-21 8:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 8:58 Christoph Hellwig [this message]
2017-05-21 18:11 ` is alpha jensen support dead? Bob Tracy
2017-05-21 18:11 ` Bob Tracy
2017-05-22 7:51 ` Christoph Hellwig
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=20170521085848.GA14559@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=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).