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: <20070823223833.65fba17e.randy.dunlap@oracle.com>
Date:	Thu, 23 Aug 2007 22:38:33 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Shannon Nelson <shannon.nelson@...el.com>
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	davem@...emloft.net
Subject: Re: [PATCH v2 -mm 3/7] I/OAT: code cleanup from checkpatch output

On Thu, 23 Aug 2007 17:15:06 -0700 Shannon Nelson wrote:

> Take care of a bunch of little code nits in ioatdma files
> 
> Signed-off-by: Shannon Nelson <shannon.nelson@...el.com>
> Acked-by: David S. Miller <davem@...emloft.net>
> ---
> 
>  drivers/dma/ioat_dma.c |  200 +++++++++++++++++++++++++++---------------------
>  1 files changed, 111 insertions(+), 89 deletions(-)
> 
> diff --git a/drivers/dma/ioat_dma.c b/drivers/dma/ioat_dma.c
> index 55227d4..9a4d154 100644
> --- a/drivers/dma/ioat_dma.c
> +++ b/drivers/dma/ioat_dma.c

> -	printk(KERN_INFO "Intel(R) I/OAT DMA Engine found, %d channels\n",
> -		device->common.chancnt);
> +	printk(KERN_INFO " "
> +		 "ioatdma: Intel(R) I/OAT DMA Engine found, %d channels\n",
> +		 device->common.chancnt);
>  
>  	err = ioat_self_test(device);
>  	if (err)

> @@ -764,7 +784,8 @@ err_set_dma_mask:
>  	pci_disable_device(pdev);
>  err_enable_device:
>  
> -	printk(KERN_ERR "Intel(R) I/OAT DMA Engine initialization failed\n");
> +	printk(KERN_INFO " "
> +		"ioatdma: Intel(R) I/OAT DMA Engine initialization failed\n");
>  
>  	return err;
>  }

What's with these (KERN_INFO " "
			"...more strings");
??

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
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