public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: matthew@wil.cx
Cc: linux-arch@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	cneira@srb.cl
Subject: Re: sys_pciconfig_{read,write}
Date: Fri, 20 Jan 2006 02:00:32 -0800 (PST)	[thread overview]
Message-ID: <20060120.020032.119957438.davem@davemloft.net> (raw)
In-Reply-To: <20060109162718.GP19769@parisc-linux.org>

From: Matthew Wilcox <matthew@wil.cx>
Date: Mon, 9 Jan 2006 09:27:18 -0700

[ Going through some old emails I intended to get to before
  heading off to linux.conf.au :-) ]

> So I propose the following three patches:
> 
> 1/ New Kconfig symbol CONFIG_PCI_SYSCALLS to be defined by the above
> architectures.  Makefile altered accordingly.
> 
> 2/ Removal of BKL from syscall implementation.
> 
> 3/ Removal of !CONFIG_PCI pciconfig stubs from alpha, ia64 and sparc64
> (we already have cond_syscalls for them).

Sounds fine to me.

> I don't quite understand why we need
> compat_sys_pciconfig_{read,write,iobase} on ppc64.  Can't these just
> call the normal versions?

I don't see this in the current tree, were they removed as
a result of this observation?

  parent reply	other threads:[~2006-01-20 10:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 16:27 sys_pciconfig_{read,write} Matthew Wilcox
2006-01-09 23:36 ` Subject: [PATCH] powerpc: remove compat_sys_pciconfig_* Stephen Rothwell
2006-01-09 23:37 ` sys_pciconfig_{read,write} Stephen Rothwell
2006-01-20 10:00 ` David S. Miller [this message]
2006-01-20 12:10   ` sys_pciconfig_{read,write} Geert Uytterhoeven

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=20060120.020032.119957438.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=cneira@srb.cl \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=matthew@wil.cx \
    /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