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
Le 18/02/2017 à 14:06, Greg Kroah-Hartman a écrit :
On Sat, Feb 18, 2017 at 09:35:36AM +0100, Romain Perier wrote:
quoted
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
Hi,
I was not sure about this. I have noticed that most of the API changes
are tagged as RFC.
I can re-send a v3 without the prefix RFC if you prefer.
Thanks,
Romain
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html