linux-kernel - Re: [GIT PULL] x86/entry for 7.0-rc1

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]

Message-ID: <8853ba3f-09c6-4e57-8c33-a9f2fd60bbd7@zytor.com>
Date: Wed, 11 Feb 2026 11:22:52 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] x86/entry for 7.0-rc1

On 2026-02-11 09:52, Linus Torvalds wrote:
> On Wed, 11 Feb 2026 at 09:40, H. Peter Anvin <hpa@...or.com> wrote:
>>
>> Oh, I do too. And so I do make in the build directory, or tack on the O=
>> option. FAR more annoying to me is that kbuild requires you to do the make
>> command in the root directory of the tree.
> 
> It would indeed be lovely if "make" in subdirectories would find their
> way back home.
> 
>> "make -C ../../../../.. arch/x86/entry/vdso/vdso32/sigreturn.o" is not really
>> much better than
> 
> Yeah, I live in the top directory most of the time, so I go the other
> way and just do
> 
>    make arch/x86/entry/vdso/vdso32/sigreturn.o
> 
> or whatever path I'm interested in (sometimes just a whole subdirectory).
> 
> And then I depend on good autocomplete of filenames, so I never
> actually type out that full path.
> 
I just wrote up a script called kmake and added it to my scripts repository:

	https://git.zytor.com/linux/ktest/tree/bin/kmake

	-hpa