linux-kernel - Re: [PATCH 06/18] x86 vDSO: arch/x86/vdso/vdso32

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: <20071120205759.3533A26F8BE@magilla.localdomain>
Date:	Tue, 20 Nov 2007 12:57:59 -0800 (PST)
From:	Roland McGrath <roland@...hat.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 06/18] x86 vDSO: arch/x86/vdso/vdso32

> >  rename arch/x86/{kernel/vsyscall-int80_32.S => vdso/vdso32/int80.S} (97%)
> >  rename arch/x86/{kernel/vsyscall-note_32.S => vdso/vdso32/note.S} (95%)
> >  rename arch/x86/{kernel/vsyscall-sigreturn_32.S => vdso/vdso32/sigreturn.S} (100%)
> >  rename arch/x86/{kernel/vsyscall-sysenter_32.S => vdso/vdso32/sysenter.S} (99%)
> 
> I just stumbled accross those renames, when I tried to apply your
> series from the mailbox. I guess there is some option to git which
> creates a real patch. I fixed it up manually for now.

You don't have to do anything manual.  git-apply handles these fine.
>From my introduction post (00/18):

	There are several renames in here, so GIT can apply them but maybe patch
	can't.  (If there is a switch to git-format-patch to produce something
	more universally applicable, I haven't found it.)



Thanks,
Roland
-
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/