linux-kernel - Re: [PATCH 1/5] Codying style fixes in ./arch/x86/ia32

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 8 Jan 2008 11:24:15 +0100
From:	"Paolo Ciarrocchi" <paolo.ciarrocchi@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
	"Linux Kernel" <linux-kernel@...r.kernel.org>, trivial@...nel.org
Subject: Re: [PATCH 1/5] Codying style fixes in ./arch/x86/ia32

On Jan 8, 2008 11:20 AM, Ingo Molnar <mingo@...e.hu> wrote:
>
> * Paolo Ciarrocchi <paolo.ciarrocchi@...il.com> wrote:
>
> >  int ia32_classify_syscall(unsigned syscall)
> >  {
> > -       switch(syscall) {
> > +       switch (syscall) {
> >         case __NR_open:
> >                 return 2;
> >         case __NR_openat:
>
> this patch has whitespace damage. (tabs got converted to spaces)
>
> i fixed this up, but the other patches in your queue are corrupted too,
> they have linewraps and tabs->spaces problems as well.

:-/ Sorry about that, I fwed the patch queue with gmail.

> also, please use unique subjects for your patches. Instead of:
>
>   Subject: Codying style fixes in ./arch/x86/ia32
>
> use:
>
>   Subject: x86: coding style fixes in arch/x86/ia32/audit.c
>
> (also please keep them lower case)

OK, will do that when I'll back home.

And I'll send the patch queue using a proper MUA :-)

Thanks.

Ciao,
-- 
Paolo
http://paolo.ciarrocchi.googlepages.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/