All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: 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: Wed, 8 Sep 2010 08:05:57 +0200	[thread overview]
Message-ID: <20100908080557.511d307b@basil.nowhere.org> (raw)
In-Reply-To: <4C86B860.1070105@suse.cz>


> 
> Hmm, the changelog says:
> The warning I saw was actually for the PCMCIA aha152x driver.
> 
> which I think are compiler warnings. But I see only one emitted by the
> compiler and it is in a debug print.


Don't remember the exact warning, but I was rather trigger happy
on getting rid of all these ancient unmaintained drivers on 64bit 
back then.

In hindsight it was the right thing to do -- their userbase
seems to be near zero and there were little to no complains 
about it ever.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

  reply	other threads:[~2010-09-08  6:06 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 [this message]
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=20100908080557.511d307b@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=bharrosh@panasas.com \
    --cc=fischer@linux-buechse.de \
    --cc=jslaby@suse.cz \
    --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.