From: Matt Turner <mattst88@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Richard Henderson <rth@twiddle.net>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-alpha <linux-alpha@vger.kernel.org>,
linux-arch@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: is alpha jensen support dead?
Date: Sun, 21 May 2017 22:33:33 -0700 [thread overview]
Message-ID: <CAEdQ38F4aKXX4aDStWB5GEfCUfQ1Aige7i1_Pev8CMUtN02faw@mail.gmail.com> (raw)
In-Reply-To: <20170521085848.GA14559@lst.de>
On Sun, May 21, 2017 at 1:58 AM, Christoph Hellwig <hch@lst.de> wrote:
> 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.
I haven't had time for alpha stuff in quite a while.
I've never even had a Jensen, so it's never been important to me personally.
next prev parent reply other threads:[~2017-05-22 5:33 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
2017-06-05 12:49 ` Maciej W. Rozycki
2017-06-05 12:49 ` Maciej W. Rozycki
2017-05-22 5:33 ` Matt Turner [this message]
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=CAEdQ38F4aKXX4aDStWB5GEfCUfQ1Aige7i1_Pev8CMUtN02faw@mail.gmail.com \
--to=mattst88@gmail.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=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).