From: Christoph Hellwig <hch@infradead.org>
To: Cai Huoqing <caihuoqing@baidu.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: Remove the unused pci wrappers pci_pool_xxx()
Date: Mon, 18 Oct 2021 03:30:17 -0700 [thread overview]
Message-ID: <YW1MuU8GfGuIAzR1@infradead.org> (raw)
In-Reply-To: <20211018081629.151-1-caihuoqing@baidu.com>
On Mon, Oct 18, 2021 at 04:16:28PM +0800, Cai Huoqing wrote:
> The wrappers around dma_pool_xxx should go away, so
> remove the unused pci wrappers.
> Prefer using dma_pool_xxx() instead of the pci wrappers
> pci_pool_xxx(), and the use of pci_pool_xxx was already
> removed.
>
> Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
This looks good.
But did this survive a few rounds of buildbot randomconfig build on
various architectures? I'd be somewhat surprised if no file at all
dependended on this implicit inclusion of dmapool.h.
next prev parent reply other threads:[~2021-10-18 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 8:16 [PATCH] PCI: Remove the unused pci wrappers pci_pool_xxx() Cai Huoqing
2021-10-18 10:30 ` Christoph Hellwig [this message]
2021-10-18 12:17 ` kernel test robot
2021-10-18 12:45 ` kernel test robot
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=YW1MuU8GfGuIAzR1@infradead.org \
--to=hch@infradead.org \
--cc=bhelgaas@google.com \
--cc=caihuoqing@baidu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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