linux-kernel - Re: [PATCH 2/8] integrity: fix checkpatch errors

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:	Mon, 03 Mar 2014 09:23:13 -0500
From:	Mimi Zohar <zohar@...ux.vnet.ibm.com>
To:	Dmitry Kasatkin <dmitry.kasatkin@...il.com>
Cc:	Dmitry Kasatkin <d.kasatkin@...sung.com>,
	linux-security-module@...r.kernel.org,
	James Morris <jmorris@...ei.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	casey.schaufler@...el.com
Subject: Re: [PATCH 2/8] integrity: fix checkpatch errors

On Mon, 2014-03-03 at 16:01 +0200, Dmitry Kasatkin wrote: 
> On Mon, Mar 3, 2014 at 3:41 PM, Mimi Zohar <zohar@...ux.vnet.ibm.com> wrote:
> > On Fri, 2014-02-28 at 16:59 +0200, Dmitry Kasatkin wrote:
> >> Unfixed checkpatch errors make it difficult to see new errors..
> >> This patch fix them.
> >
> > A number of these errors are a result of inconsistencies between Lindent
> > and checkpatch.  This patch uses the checkpatch preferences.
> >
> >> Some lines with over 80 chars remained unchanged to improve
> >> code readability.
> >>
> >> Signed-off-by: Dmitry Kasatkin <d.kasatkin@...sung.com>
> >
> > This patch doesn't apply cleanly to either linux-integrity/next-fixes or
> > to linux-security/next.
> >
> > thanks,
> >
> 
> Hi,
> 
> Did you apply  Joe Perches's patch what you signed-off first?

Thanks for the reminder. I hadn't applied Joe's patch, but that didn't
resolve it.

Mimi

--
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/