From: Greg KH <greg@kroah.com>
To: Deepak Saxena <dsaxena@plexity.net>
Cc: torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Replace pci_pool with generic dma_pool
Date: Fri, 30 Jan 2004 17:05:15 -0800 [thread overview]
Message-ID: <20040131010515.GH10860@kroah.com> (raw)
In-Reply-To: <20040131003205.GA24967@plexity.net>
On Fri, Jan 30, 2004 at 05:32:05PM -0700, Deepak Saxena wrote:
>
> All,
>
> This set of patches against 2.6.2-rc2 removes the PCI-specific pci_pool
> structure and replaces it with a generic dma_pool. For compatibility with
> existing PCI drivers, macros are provided that map pci_pool_* to dma_pool_*.
> This is extremely useful for architecture that have non-PCI devices but
> require DMA buffer pools. A good example is USB, where we've had to make
> some hacks in the ARM implementation of the DMA API to get around the
> USB's usage of the PCI DMA API and pci_pools with non-PCI device.
> The patch has been tested on x86, ppc, and xscale (ARM).
>
> Patch portions are posted as replies to this email.
>
> If this patch is accepted, I'll post a follow-on patch to the USB list
> to clean up the USB layer to only use the generic DMA functions instead
> of the PCI functions.
These patches look sane. I'll apply them to my PCI tree this weekend,
which will propagate to the -mm tree. If nothing breaks there, I'll
send them on to Linus after 2.6.2 comes out.
thanks a lot for this.
greg k-h
next prev parent reply other threads:[~2004-01-31 1:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-31 0:32 [PATCH] Replace pci_pool with generic dma_pool Deepak Saxena
2004-01-31 0:37 ` [PATCH 1/3] " Deepak Saxena
2004-01-31 0:39 ` [PATCH 2/3] " Deepak Saxena
2004-01-31 0:41 ` [PATCH 3/3] " Deepak Saxena
2004-01-31 1:05 ` Greg KH [this message]
2004-02-02 19:02 ` [PATCH] " Greg KH
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=20040131010515.GH10860@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=dsaxena@plexity.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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