public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] objtool changes for v5.19
Date: Tue, 24 May 2022 08:02:27 +0200	[thread overview]
Message-ID: <Yox088fRrhh4grBX@gmail.com> (raw)
In-Reply-To: <Yoxucp7aUrCaV9uE@gmail.com>


* Ingo Molnar <mingo@kernel.org> wrote:

>  34 files changed, 959 insertions(+), 684 deletions(-)

Note that with your latest tree you'll get 3 new conflicts:

  CONFLICT (content): Merge conflict in scripts/link-vmlinux.sh
  CONFLICT (content): Merge conflict in scripts/Makefile.build
  CONFLICT (content): Merge conflict in arch/x86/Kconfig

If you want to double check, you can find our resolution in tip:x86/merge:

  a1df7cc57786 Merge branch 'objtool/core' into x86/merge, to resolve conflicts

At:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/merge # INTERNAL MERGE TREE, DO NOT PULL

Here's the merge description:

 ===================
 The following commits between objtool/core and various x86 branches conflict:

   968b493173ac x86/mm: Make DMA memory shared for TD guest
   77a512e35db7 x86/boot: Avoid #VE during boot for TDX platforms
   65fab5bc033a x86/tdx: Exclude shared bit from __PHYSICAL_MASK
   41394e33f3a0 x86/tdx: Extend the confidential computing API to support TDX guests
   59bd54a84d15 x86/tdx: Detect running as a TDX guest in early boot
   dbae0a934f09 x86/cpu: Remove CONFIG_X86_SMAP and "nosmap"

 and:

   753da4179d08 objtool: Remove --lto and --vmlinux in favor of --link
   489e355b4225 objtool: Add HAVE_NOINSTR_VALIDATION
   0f620cefd775 objtool: Rename "VMLINUX_VALIDATION" -> "NOINSTR_VALIDATION"
   22102f4559be objtool: Make noinstr hacks optional
   4ab7674f5951 objtool: Make jump label hack optional
   26e176896a5b objtool: Make static call annotation optional
   720644749647 objtool: Make stack validation frame-pointer-specific
   03f16cd020eb objtool: Add CONFIG_OBJTOOL
   7dce62041ac3 objtool: Make stack validation optional
   b51277eb9775 objtool: Ditch subcommands
   2daf7faba7de objtool: Reorganize cmdline options
   4cdfc11b2836 x86/Kconfig: fix the spelling of 'becoming' in X86_KERNEL_IBT config
   4a5de9b76fcb objtool: Enable unreachable warnings for CLANG LTO

 Resolve them:

  - overlapping modifications
  - modifying removed functionality

 Conflicts:
	arch/x86/Kconfig
	scripts/Makefile.build
	scripts/link-vmlinux.sh
 ===================

Thanks,

	Ingo

  reply	other threads:[~2022-05-24  6:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 16:32 [GIT PULL] objtool changes for v5.19 Ingo Molnar
2022-05-24  5:34 ` Ingo Molnar
2022-05-24  6:02   ` Ingo Molnar [this message]
2022-05-24 17:53     ` Linus Torvalds
2022-05-24 18:08       ` Peter Zijlstra
2022-05-24 18:14         ` Josh Poimboeuf
2022-05-24 19:53 ` pr-tracker-bot

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=Yox088fRrhh4grBX@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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