From: Joe Perches <joe@perches.com>
To: Romain Perier <romain.perier@collabora.com>,
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>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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: [PATCH v4 00/19] Replace PCI pool by DMA pool API
Date: Wed, 01 Mar 2017 11:29:11 -0800 [thread overview]
Message-ID: <1488396551.20731.5.camel@perches.com> (raw)
In-Reply-To: <20170301155521.30281-1-romain.perier@collabora.com>
On Wed, 2017-03-01 at 16:55 +0100, Romain Perier wrote:
> support to warn about this old API in checkpath.pl
checkpatch
This part isn't true anymore, but it seems sensible enough, thanks.
prev parent reply other threads:[~2017-03-01 19:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 15:55 [PATCH v4 00/19] Replace PCI pool by DMA pool API Romain Perier
2017-03-01 15:55 ` [PATCH v4 01/19] block: DAC960: Replace PCI pool old API Romain Perier
2017-03-01 15:55 ` [PATCH v4 02/19] dmaengine: pch_dma: " Romain Perier
2017-03-01 15:55 ` [PATCH v4 03/19] IB/mthca: " Romain Perier
2017-03-01 15:55 ` [PATCH v4 04/19] net: e100: " Romain Perier
2017-03-01 15:55 ` [PATCH v4 05/19] mlx4: " Romain Perier
2017-03-01 15:55 ` [PATCH v4 06/19] mlx5: " Romain Perier
2017-03-01 15:55 ` [PATCH v4 07/19] wireless: ipw2200: " Romain Perier
2017-03-01 15:55 ` [PATCH v4 08/19] scsi: be2iscsi: " Romain Perier
2017-03-03 9:30 ` Sergei Shtylyov
2017-03-01 15:55 ` [PATCH v4 09/19] scsi: csiostor: " Romain Perier
2017-03-03 9:27 ` Sergei Shtylyov
2017-03-01 15:55 ` [PATCH v4 10/19] scsi: lpfc: " Romain Perier
2017-03-01 15:55 ` [PATCH v4 11/19] scsi: megaraid: " Romain Perier
2017-03-02 6:55 ` Sumit Saxena
2017-03-01 15:55 ` [PATCH v4 12/19] scsi: mpt3sas: " Romain Perier
2017-03-01 15:55 ` [PATCH v4 13/19] scsi: mvsas: " Romain Perier
2017-03-01 15:55 ` [PATCH v4 14/19] scsi: pmcraid: " Romain Perier
2017-03-01 15:55 ` [PATCH v4 15/19] usb: gadget: amd5536udc: " Romain Perier
2017-03-01 15:55 ` [PATCH v4 16/19] usb: gadget: net2280: " Romain Perier
2017-03-01 15:55 ` [PATCH v4 17/19] usb: gadget: pch_udc: " Romain Perier
2017-03-01 15:55 ` [PATCH v4 18/19] usb: host: Remove remaining pci_pool in comments Romain Perier
2017-03-01 15:55 ` [PATCH v4 19/19] PCI: Remove PCI pool macro functions Romain Perier
2017-03-01 19:29 ` Joe Perches [this message]
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=1488396551.20731.5.camel@perches.com \
--to=joe@perches.com \
--cc=balbi@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).