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]
Message-ID: <20101126110111.GG5520@sortiz-mobl>
Date:	Fri, 26 Nov 2010 12:01:12 +0100
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	Joe Perches <joe@...ches.com>
Cc:	Jiri Kosina <trivial@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 06/14] drivers/mfd: Use printf extension %pR for struct
 resource

Hi Joe,

On Fri, Nov 12, 2010 at 01:37:56PM -0800, Joe Perches wrote:
> Using %pR standardizes the struct resource output.
> 
> Signed-off-by: Joe Perches <joe@...ches.com>
Patch applied, thanks.

Cheers,
Samuel.


> ---
>  drivers/mfd/sm501.c |    7 ++-----
>  1 files changed, 2 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/mfd/sm501.c b/drivers/mfd/sm501.c
> index bc9275c..78638cf 100644
> --- a/drivers/mfd/sm501.c
> +++ b/drivers/mfd/sm501.c
> @@ -745,11 +745,8 @@ static int sm501_register_device(struct sm501_devdata *sm,
>  	int ret;
>  
>  	for (ptr = 0; ptr < pdev->num_resources; ptr++) {
> -		printk(KERN_DEBUG "%s[%d] flags %08lx: %08llx..%08llx\n",
> -		       pdev->name, ptr,
> -		       pdev->resource[ptr].flags,
> -		       (unsigned long long)pdev->resource[ptr].start,
> -		       (unsigned long long)pdev->resource[ptr].end);
> +		printk(KERN_DEBUG "%s[%d] %pR\n",
> +		       pdev->name, ptr, &pdev->resource[ptr]);
>  	}
>  
>  	ret = platform_device_register(pdev);
> -- 
> 1.7.3.1.g432b3.dirty
> 

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ