The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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 09:39:13 -0800	[thread overview]
Message-ID: <712d7389-d744-4e0d-a1a3-2b938de55aaa@zytor.com> (raw)
In-Reply-To: <CAHk-=wjOsk8ddzcCE0NvTQ4+CEznBFuB99DoyM4r1baavEyw=A@mail.gmail.com>

On 2026-02-11 09:05, Linus Torvalds wrote:
> 
> I often actually look at the build results. Not the object files, no.
> But I do things like
> 
>    make xyz/file.s
> 
> *ALL* the time when developing, and I just don't want to have to treat
> the "this was what I just generated" and "this was what I generated it
> from" as something very different.
> 
> Admittedly, these days I don't do much actual development, so I guess
> I wouldn't care.
> 
> Which reminds me that I need to go back to merging...
> 

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.

"make -C ../../../../.. arch/x86/entry/vdso/vdso32/sigreturn.o" is not really
much better than

"make -C ../../../../.. O=o/x86_64.cf arch/x86/entry/vdso/vdso32/sigreturn.o"

Come to think of it, I really should just wrap that up in a script...

If anyone is interested, my scripts are sitting at:

	git://git.zytor.com/linux/ktest.git

	-hpa


  reply	other threads:[~2026-02-11 17:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09 21:09 [GIT PULL] x86/entry for 7.0-rc1 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 [this message]
2026-02-11 17:52               ` Linus Torvalds
2026-02-11 19:22                 ` H. Peter Anvin
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=712d7389-d744-4e0d-a1a3-2b938de55aaa@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