linux-kernel - Re: [PATCH resent v2 1/2] ioport : add DEFINE_RES_DMA_SIZE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 19 Jan 2012 16:14:29 +0800
From:	Shawn Guo <shawn.guo@...aro.org>
To:	Huang Shijie <b32955@...escale.com>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, u.kleine-koenig@...gutronix.de
Subject: Re: [PATCH resent v2 1/2] ioport : add DEFINE_RES_DMA_SIZE_NAMED
 macro

On Thu, Jan 19, 2012 at 03:53:39PM +0800, Huang Shijie wrote:
> Some DMA resource does have the range more then ones.
> 
I'm not sure the patch is welcomed.  You may want to just use
DEFINE_RES_NAMED for such cases.

Regards,
Shawn

> Signed-off-by: Huang Shijie <b32955@...escale.com>
> ---
>  include/linux/ioport.h |    4 +++-
>  1 files changed, 3 insertions(+), 1 deletions(-)
> 
> diff --git a/include/linux/ioport.h b/include/linux/ioport.h
> index 9d57a71..9ea5de4 100644
> --- a/include/linux/ioport.h
> +++ b/include/linux/ioport.h
> @@ -134,8 +134,10 @@ struct resource_list {
>  #define DEFINE_RES_IRQ(_irq)						\
>  	DEFINE_RES_IRQ_NAMED((_irq), NULL)
>  
> +#define DEFINE_RES_DMA_SIZE_NAMED(_dma, _size, _name)			\
> +	DEFINE_RES_NAMED((_dma), (_size), (_name), IORESOURCE_DMA)
>  #define DEFINE_RES_DMA_NAMED(_dma, _name)				\
> -	DEFINE_RES_NAMED((_dma), 1, (_name), IORESOURCE_DMA)
> +	DEFINE_RES_DMA_SIZE_NAMED((_dma), 1, (_name))
>  #define DEFINE_RES_DMA(_dma)						\
>  	DEFINE_RES_DMA_NAMED((_dma), NULL)
>  
> -- 
> 1.7.0.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/