public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Linus Torvalds <torvalds@transmeta.com>,
	Matthew Dobson <colpatch@us.ibm.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org,
	Michael Hohnbaum <hohnbaum@us.ibm.com>,
	Greg KH <gregkh@us.ibm.com>
Subject: Re: [patch] PCI Cleanup
Date: Tue, 13 Aug 2002 12:57:32 -0700	[thread overview]
Message-ID: <2011880000.1029268652@flay> (raw)
In-Reply-To: <Pine.LNX.4.44.0208131013060.7411-100000@home.transmeta.com>

> Quite frankly, to me it looks like the real issue is that you don't want 
> to have the byte/word/dword stuff replicated three times.

Exactly - we can do that, but it just seems messy.
 
> And your cleanup avoids the replication, but I think it has other badness 
> in it: in particular it depends on those two global pointers. Which makes 
> it really hard to have (for example) per-segment functions, or hard for 
> drivers to hook into it (there's one IDE driver in particular that wants 
> to do conf2 accesses, and nothing else. So it duplicates its own conf2 
> functions right now, because it has no way to hook into the generic ones).

OK, that IDE thing smacks of unmitigated evil to me, but if things are relying 
on it, we shouldn't change it.
 
>   And I'd suggest multiplexing them at a higher level. Instead of 
>   six different pcibios_read_config_byte etc functions, move the 
>   multiplexing up, make make them just two functions at _that_ level (and 
>   make siz #defines to make it compatible with existing users).

Yup, that sounds like ultimately the correct thing to do. Will try to get
that way done instead. Should clean things up nicely ....

M.




  reply	other threads:[~2002-08-13 19:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-13  0:08 [patch] PCI Cleanup Matthew Dobson
2002-08-13 11:45 ` Alan Cox
2002-08-13 14:17   ` Martin J. Bligh
2002-08-13 14:57     ` Alan Cox
2002-08-13 15:15       ` Martin J. Bligh
2002-08-13 17:00       ` Matthew Dobson
2002-08-13 17:23         ` Linus Torvalds
2002-08-13 19:57           ` Martin J. Bligh [this message]
2002-08-13 20:13             ` Alan Cox
2002-08-13 20:26               ` Linus Torvalds
2002-08-13 22:29                 ` Matthew Dobson
2002-08-13 22:46                   ` Linus Torvalds
2002-08-14  0:57                     ` Matthew Dobson
2002-08-15  0:23                     ` Matthew Dobson
2002-08-14  7:08               ` Martin Mares
2002-08-13 14:55   ` Martin J. Bligh
2002-08-13 15:07     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-08-15  2:24 Grover, Andrew
2002-08-15  7:49 ` Martin Mares
2002-08-15 15:58 ` Kai Germaschewski
2002-08-15 16:36   ` Greg KH
2002-08-16 22:34     ` Greg KH
2002-08-19 23:41       ` Matthew Dobson
2002-08-15 18:28 ` Patrick Mochel
2002-08-15 20:23 Grover, Andrew
2002-08-15 20:54 ` Patrick Mochel

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=2011880000.1029268652@flay \
    --to=martin.bligh@us.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=colpatch@us.ibm.com \
    --cc=gregkh@us.ibm.com \
    --cc=hohnbaum@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox