Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1588626 > unrolled thread

Re: [PATCH v3 18/20] usb: host: Remove remaining pci_pool in comments

Started byPeter Senna Tschudin <peter.senna@collabora.com>
First post2017-02-27 12:50 +0100
Last post2017-02-27 12:50 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v3 18/20] usb: host: Remove remaining pci_pool in comments Peter Senna Tschudin <peter.senna@collabora.com> - 2017-02-27 12:50 +0100

#1588626 — Re: [PATCH v3 18/20] usb: host: Remove remaining pci_pool in comments

FromPeter Senna Tschudin <peter.senna@collabora.com>
Date2017-02-27 12:50 +0100
SubjectRe: [PATCH v3 18/20] usb: host: Remove remaining pci_pool in comments
Message-ID<tfrYv-4Xq-21@gated-at.bofh.it>
On Sun, Feb 26, 2017 at 08:24:23PM +0100, Romain Perier wrote:
> This replaces remaining occurences of pci_pool by dma_pool, as
> this is the new API that could be used for that purpose.
> 
Reviewed-by: Peter Senna Tschudin <peter.senna@collabora.com>
> Signed-off-by: Romain Perier <romain.perier@collabora.com>
> ---
>  drivers/usb/host/ehci-hcd.c     | 2 +-
>  drivers/usb/host/fotg210-hcd.c  | 2 +-
>  drivers/usb/host/oxu210hp-hcd.c | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/usb/host/ehci-hcd.c b/drivers/usb/host/ehci-hcd.c
> index ac2c4ea..6e834b83 100644
> --- a/drivers/usb/host/ehci-hcd.c
> +++ b/drivers/usb/host/ehci-hcd.c
> @@ -597,7 +597,7 @@ static int ehci_run (struct usb_hcd *hcd)
>  	/*
>  	 * hcc_params controls whether ehci->regs->segment must (!!!)
>  	 * be used; it constrains QH/ITD/SITD and QTD locations.
> -	 * pci_pool consistent memory always uses segment zero.
> +	 * dma_pool consistent memory always uses segment zero.
>  	 * streaming mappings for I/O buffers, like pci_map_single(),
>  	 * can return segments above 4GB, if the device allows.
>  	 *
> diff --git a/drivers/usb/host/fotg210-hcd.c b/drivers/usb/host/fotg210-hcd.c
> index 1c5b34b..ced08dc 100644
> --- a/drivers/usb/host/fotg210-hcd.c
> +++ b/drivers/usb/host/fotg210-hcd.c
> @@ -5047,7 +5047,7 @@ static int fotg210_run(struct usb_hcd *hcd)
>  	/*
>  	 * hcc_params controls whether fotg210->regs->segment must (!!!)
>  	 * be used; it constrains QH/ITD/SITD and QTD locations.
> -	 * pci_pool consistent memory always uses segment zero.
> +	 * dma_pool consistent memory always uses segment zero.
>  	 * streaming mappings for I/O buffers, like pci_map_single(),
>  	 * can return segments above 4GB, if the device allows.
>  	 *
> diff --git a/drivers/usb/host/oxu210hp-hcd.c b/drivers/usb/host/oxu210hp-hcd.c
> index bcf531c..ed20fb3 100644
> --- a/drivers/usb/host/oxu210hp-hcd.c
> +++ b/drivers/usb/host/oxu210hp-hcd.c
> @@ -2708,7 +2708,7 @@ static int oxu_run(struct usb_hcd *hcd)
>  
>  	/* hcc_params controls whether oxu->regs->segment must (!!!)
>  	 * be used; it constrains QH/ITD/SITD and QTD locations.
> -	 * pci_pool consistent memory always uses segment zero.
> +	 * dma_pool consistent memory always uses segment zero.
>  	 * streaming mappings for I/O buffers, like pci_map_single(),
>  	 * can return segments above 4GB, if the device allows.
>  	 *
> -- 
> 2.9.3
> 

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web