linux-kernel - Re: [PATCH] staging: sm7xx: code improvements and cleanup

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: <20120425205532.GA9642@kroah.com>
Date:	Wed, 25 Apr 2012 13:55:32 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	"Javier M. Mellid" <jmunhoz@...lia.com>
Cc:	gewang@...iconmotion.com, boyod.yang@...iconmotion.com.cn,
	wuzhangjin@...il.com, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: sm7xx: code improvements and cleanup

On Wed, Apr 25, 2012 at 10:50:28PM +0200, Javier M. Mellid wrote:
> This patch implements some code improvements and cleanup.
> 
> New code uses dynamic debug support. Old debug calls updated/tested to
> use this API.
> 
> Cleanup on obsolete references, internal versions and some
> comments. Dead code removal.
> 
> Patch tested with SM712.
> 
> Changes:
> 
> - Code improvements and cleanup
> - Use dynamic debug support
> - Remove out-of-date comments/references
> - Remove dead code

Can you please break this down into individual patches, each doing only
one thing, so that we can review it easier?  Otherwise, it's quite
difficult, which is one reason why we require patches to be created this
way.

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/