linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: =?unknown-8bit?B?SvxyZ2VuIEUu?= Fischer <fischer@norbit.de>
To: linux-scsi@vger.kernel.org
Subject: Re: Why is AHA152X_CS !64BIT?
Date: Thu, 9 Sep 2010 22:01:01 +0200	[thread overview]
Message-ID: <20100909200101.GA19568@linux-buechse.de> (raw)
In-Reply-To: <4C86B9A6.2050808@suse.cz>

Hi Jiri,

On Wed, Sep 08, 2010 at 00:16:06 +0200, Jiri Slaby wrote:
> As I wrote few minutes ago, there is only one which is in print. And I
> cannot find anybody fixing anything similar since 2.1.
 
> So can we enable it on 64-bit when we have two reports it works on
> 64-bit? (Is it still maintained? MAINTAINERS says so...)

For the maintainance: My ISA machine is defunct, but I still have a
PCMCIA card to test and debug it needed - although no 64bit machine with
a PCMCIA slot.

I suppose the hardware is so hardly used nowadays, that there simply
hasn't been any need for aha152x specific changes (or debugging) for
years.  And all the interface updates were done by whoever changed the
generic interface and I eventually ceased to follow.

So I guess the maintainance state should be changed to "Odd fixes" at
best.


Juergen

  reply	other threads:[~2010-09-09 20:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23 19:59 Why is AHA152X_CS !64BIT? Jiri Slaby
2010-08-30 11:13 ` Boaz Harrosh
2010-09-07 21:12   ` Konrad Rzeszutek Wilk
2010-09-07 21:41     ` Randy Dunlap
2010-09-07 21:48       ` Randy Dunlap
2010-09-07 22:10         ` James Bottomley
2010-09-07 22:16           ` Jiri Slaby
2010-09-09 20:01             ` =?unknown-8bit?B?SvxyZ2VuIEUu?= Fischer [this message]
2010-09-07 22:10         ` Jiri Slaby
2010-09-08  6:05           ` Andi Kleen
2010-09-08 15:30             ` James Bottomley
2010-09-09  6:50               ` Andi Kleen
2010-09-24 19:55                 ` Jiri Slaby

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=20100909200101.GA19568@linux-buechse.de \
    --to=fischer@norbit.de \
    --cc=fischer@linux-buechse.de \
    --cc=linux-scsi@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 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).