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

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

Message-ID: <CAHk-=wgBmHrMfGpbGMWuxoqNRB-4Ei+beTZ9RF9coSYvFVJ-oQ@mail.gmail.com>
Date: Wed, 11 Feb 2026 09:52:08 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: "H. Peter Anvin" <hpa@...or.com>
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 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.

              Linus