From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] x86/entry for 7.0-rc1
Date: Wed, 11 Feb 2026 11:22:52 -0800 [thread overview]
Message-ID: <8853ba3f-09c6-4e57-8c33-a9f2fd60bbd7@zytor.com> (raw)
In-Reply-To: <CAHk-=wgBmHrMfGpbGMWuxoqNRB-4Ei+beTZ9RF9coSYvFVJ-oQ@mail.gmail.com>
On 2026-02-11 09:52, Linus Torvalds wrote:
> On Wed, 11 Feb 2026 at 09:40, H. Peter Anvin <hpa@zytor.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
next prev parent reply other threads:[~2026-02-11 19:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 21:09 Dave Hansen
2026-02-11 3:57 ` pr-tracker-bot
2026-02-11 4:24 ` Linus Torvalds
2026-02-11 4:39 ` Linus Torvalds
2026-02-11 6:15 ` H. Peter Anvin
2026-02-11 6:34 ` Linus Torvalds
2026-02-11 16:30 ` H. Peter Anvin
2026-02-11 17:05 ` Linus Torvalds
2026-02-11 17:39 ` H. Peter Anvin
2026-02-11 17:52 ` Linus Torvalds
2026-02-11 19:22 ` H. Peter Anvin [this message]
2026-02-11 18:16 ` Andy Shevchenko
2026-02-11 18:35 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8853ba3f-09c6-4e57-8c33-a9f2fd60bbd7@zytor.com \
--to=hpa@zytor.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®