From: Jiri Slaby <jslaby@suse.cz>
To: Andi Kleen <andi@firstfloor.org>
Cc: James Bottomley <James.Bottomley@suse.de>,
Randy Dunlap <randy.dunlap@oracle.com>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
Boaz Harrosh <bharrosh@panasas.com>,
fischer@linux-buechse.de, linux-scsi@vger.kernel.org
Subject: Re: Why is AHA152X_CS !64BIT?
Date: Fri, 24 Sep 2010 22:55:34 +0300 [thread overview]
Message-ID: <4C9D0236.2030803@suse.cz> (raw)
In-Reply-To: <20100909085033.78eb4f64@basil.nowhere.org>
On 09/09/2010 09:50 AM, Andi Kleen wrote:
>> OK ... let's try it. Jiří send a patch ... and if it breaks I'm
>> handing you the pieces ...
>
> You mean reenable it? Why? Do you have any indication the user base
> of this thing (especially on 64bit) is > 0?
Yeah, I know of two people who upgraded to 64-bit recently and had been
using that driver before (the one for scanner). They both report it's
working if non-64bit condition is removed. So I will post a patch to
enable it back again...
regards,
--
js
suse labs
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-09-24 19:55 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
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 [this message]
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=4C9D0236.2030803@suse.cz \
--to=jslaby@suse.cz \
--cc=James.Bottomley@suse.de \
--cc=andi@firstfloor.org \
--cc=bharrosh@panasas.com \
--cc=fischer@linux-buechse.de \
--cc=konrad@darnok.org \
--cc=linux-scsi@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.