public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: groudier@club-internet.fr
Cc: mj@suse.cz, lk@tantalophile.demon.co.uk, davej@suse.de,
	linux-kernel@vger.kernel.org
Subject: Re: pdev_enable_device no longer used ?
Date: Mon, 11 Dec 2000 13:48:34 -0800	[thread overview]
Message-ID: <200012112148.NAA24830@pizda.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10012112116250.2023-100000@linux.local> (message from Gérard Roudier on Mon, 11 Dec 2000 21:49:52 +0100 (CET))
In-Reply-To: <Pine.LNX.4.10.10012112116250.2023-100000@linux.local>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]

   Date: 	Mon, 11 Dec 2000 21:49:52 +0100 (CET)
   From: Gérard Roudier <groudier@club-internet.fr>

   If now, the PCI stuff is claimed to be cleaned up, then _all_ the
   hacks have to be removed definitely.  As a result, the driver will
   not work anymore on Sparc64, neither on PPC and I am not sure it
   will still work on Alpha, in my opinion.

Actually Gerard, in your current 2.4.x NCR53c8xx and SYM53c8XX drivers
only real ifdefs for sparc64 are printf format strings for PCI interrupt
numbers :-)

Really, in 2.4.x sparc64 requires PCI config space hackery no longer.

Later,
David S. Miller
davem@redhat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-11 22:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-09 11:30 pdev_enable_device no longer used ? davej
2000-12-09 11:38 ` Russell King
2000-12-09 12:15   ` Ivan Kokshaysky
2000-12-09 12:36     ` davej
2000-12-09 12:53       ` Alan Cox
2000-12-09 13:08         ` davej
2000-12-09 13:44         ` Ivan Kokshaysky
2000-12-09 14:26         ` Gérard Roudier
2000-12-09 17:48           ` Russell King
2000-12-09 20:57           ` Alan Cox
2000-12-09 15:04 ` Martin Mares
2000-12-09 18:11   ` davej
2000-12-10 23:28     ` Jamie Lokier
2000-12-11  0:34       ` davej
2000-12-11 19:40         ` Gérard Roudier
2000-12-12  2:43         ` Jes Sorensen
2000-12-11 19:20       ` Gérard Roudier
2000-12-11 20:55         ` Martin Mares
2000-12-11 20:49           ` Gérard Roudier
2000-12-11 21:48             ` David S. Miller [this message]
2000-12-11 21:30               ` Gérard Roudier
2000-12-11 22:21                 ` David S. Miller
2000-12-11 22:07                   ` Gérard Roudier
2000-12-11 23:03                     ` David S. Miller
2000-12-12 19:17                       ` Gérard Roudier
2000-12-12 20:14                         ` David S. Miller
2000-12-12 20:28                           ` Gérard Roudier
2000-12-12 22:39                             ` David S. Miller
2000-12-11 23:16                     ` Martin Mares
2000-12-12 18:56                       ` Gérard Roudier
2000-12-12 12:21                   ` Adrian Cox
2000-12-12  2:39 ` Jes Sorensen

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=200012112148.NAA24830@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=davej@suse.de \
    --cc=groudier@club-internet.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk@tantalophile.demon.co.uk \
    --cc=mj@suse.cz \
    /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