From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
mochel@osdl.org, linux-kernel@vger.kernel.org
Subject: [BK PATCH] PCI reorg fix
Date: Thu, 9 May 2002 09:52:34 -0700 [thread overview]
Message-ID: <20020509165234.GA17627@kroah.com> (raw)
In-Reply-To: <200205091647.g49GlkG02757@localhost.localdomain>
Linus,
James pointed out that pci_alloc_consistent() and pci_free_consistent()
are allowed to be called, even if CONFIG_PCI is not enabled. So this
changeset moves these calls back into the arch/i386/kernel directory.
Pull from: bk://linuxusb.bkbits.net/linux-2.5-pci
As a side note, I don't think that any pci_* function should be able to
be called by non-pci drivers. Is it worth spending the time now in 2.5
to make these two functions not rely on 'struct pci_dev' and fix up all
of the drivers and architectures and documentation to reflect this?
Possible names would be alloc_consistent() and free_consistent()?
thanks,
greg k-h
ChangeSet@1.557, 2002-05-09 10:35:57-07:00, greg@kroah.com
moved the pci_alloc_consistent() and pci_free_consistent() functions back
into arch/i386/kernel as they are needed even if CONFIG_PCI is not enabled.
arch/i386/pci/dma.c | 37 -------------------------------------
arch/i386/kernel/Makefile | 2 +-
arch/i386/kernel/pci-dma.c | 37 +++++++++++++++++++++++++++++++++++++
arch/i386/pci/Makefile | 2 +-
4 files changed, 39 insertions(+), 39 deletions(-)
next prev parent reply other threads:[~2002-05-09 17:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 23:11 Problems with 2.5.14 PCI reorg and non-PCI architectures James Bottomley
2002-05-09 8:44 ` Greg KH
2002-05-09 13:00 ` James Bottomley
2002-05-09 15:23 ` Greg KH
2002-05-09 16:47 ` James Bottomley
2002-05-09 16:52 ` Greg KH [this message]
2002-05-09 18:06 ` [BK PATCH] PCI reorg fix Patrick Mochel
2002-05-09 17:15 ` Greg KH
2002-05-09 18:26 ` James Bottomley
2002-05-09 18:23 ` Kai Germaschewski
2002-05-09 18:26 ` Patrick Mochel
2002-05-09 18:46 ` Kai Germaschewski
2002-05-09 19:45 ` Martin Dalecki
2002-05-09 21:34 ` James Bottomley
2002-05-09 20:51 ` Martin Dalecki
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=20020509165234.GA17627@kroah.com \
--to=greg@kroah.com \
--cc=James.Bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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