linux-kernel - Re: [PATCH 2/4] staging/zache BUILD

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] [day] [month] [year] [list]

Date:	Mon, 18 Feb 2013 10:51:13 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Robert Berger <git.rber@...il.com>
Cc:	devel@...verdev.osuosl.org, konrad.wilk@...cle.com,
	sjenning@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
	xiaoguangrong@...ux.vnet.ibm.com, minchan@...nel.org,
	joe@...ches.com,
	Robert Berger <rber.git@...iableEmbeddedSystems.com>
Subject: Re: [PATCH 2/4] staging/zache BUILD_MODNAME and checkpatch fixes

On Sat, Feb 16, 2013 at 10:35:52AM +0200, Robert Berger wrote:
> As per Joe's suggestion:
> "Perhaps it'd be better to use KBUILD_MODNAME all the time
> instead of adding the prefix. Also, to me mixing "ramster: "
> and "zcache: " for the prefixes is odd. Just using zcache
> all the time would be simpler, so remove namestr too."
> 
> checkpatch fixes:
> zcache-main.c:1987: WARNING: quoted string split across lines
> zcache-main.c:2002: WARNING: quoted string split across lines
> 
> Signed-off-by: Robert Berger <rber.git@...iableEmbeddedSystems.com>
> ---
>  drivers/staging/zcache/zcache-main.c |  137 ++++++++++++++++------------------
>  1 file changed, 65 insertions(+), 72 deletions(-)

This patch fails to apply, care to refresh it, and your 2 other patches
in this series, against the linux-next tree, and resend it so that I can
apply it?

thanks,

greg k-h
--
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/