From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Romain Perier <romain.perier@collabora.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Doug Ledford <dledford@redhat.com>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>,
jeffrey.t.kirsher@intel.com,
"David S. Miller" <davem@davemloft.net>,
stas.yakovlev@gmail.com,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Felipe Balbi <balbi@kernel.org>,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Peter Senna Tschudin <peter.senna@collabora.co.uk>
Subject: Re: [RFC v2 00/20] Replace PCI pool by DMA pool API
Date: Sat, 18 Feb 2017 14:06:00 +0100 [thread overview]
Message-ID: <20170218130600.GA24938@kroah.com> (raw)
In-Reply-To: <20170218083556.20215-1-romain.perier@collabora.com>
On Sat, Feb 18, 2017 at 09:35:36AM +0100, Romain Perier wrote:
> The current PCI pool API are simple macro functions direct expanded to
> the appropriated dma pool functions. The prototypes are almost the same
> and semantically, they are very similar. I propose to use the DMA pool
> API directly and get rid of the old API.
>
> This set of patches, replaces the old API by the dma pool API, adds
> support to warn about this old API in checkpath.pl and remove the
> defines.
Why is this a "RFC" series? Personally, I never apply those as it
implies that the author doesn't think they are ready to be merged :)
thanks,
greg k-h
next prev parent reply other threads:[~2017-02-18 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170218083556.20215-1-romain.perier@collabora.com>
[not found] ` <20170218083556.20215-2-romain.perier@collabora.com>
2017-02-18 12:51 ` [RFC v2 01/20] block: DAC960: Replace PCI pool old API Peter Senna Tschudin
2017-02-18 13:06 ` Greg Kroah-Hartman [this message]
[not found] ` <20170218130600.GA24938-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-02-18 17:57 ` [RFC v2 00/20] Replace PCI pool by DMA pool API Romain Perier
2017-02-18 17:57 ` Romain Perier
[not found] ` <20170218083556.20215-13-romain.perier@collabora.com>
[not found] ` <20170218083556.20215-13-romain.perier-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2017-02-18 18:40 ` [RFC v2 12/20] scsi: mpt3sas: Replace PCI pool old API Peter Senna Tschudin
2017-02-18 18:40 ` Peter Senna Tschudin
2017-02-18 18:46 ` [RFC v2 00/20] Replace PCI pool by DMA pool API Peter Senna Tschudin
[not found] ` <20170218083556.20215-12-romain.perier@collabora.com>
[not found] ` <20170218083556.20215-12-romain.perier-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2017-02-18 18:37 ` [RFC v2 11/20] scsi: megaraid: Replace PCI pool old API Peter Senna Tschudin
2017-02-18 18:37 ` Peter Senna Tschudin
2017-02-18 19:11 ` Peter Senna Tschudin
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=20170218130600.GA24938@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=hal.rosenstock@gmail.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=peter.senna@collabora.co.uk \
--cc=romain.perier@collabora.com \
--cc=sean.hefty@intel.com \
--cc=stas.yakovlev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.