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, Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/cleanups for v6.6
Date: Mon, 28 Aug 2023 23:16:40 +0200	[thread overview]
Message-ID: <ZO0OuPfs0bMddVTW@gmail.com> (raw)

Linus,

Please pull the latest x86/cleanups git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-cleanups-2023-08-28

   # HEAD: 212f07a21622cbd4bb271b558b2d3ae0652e9875 x86/platform/uv: Refactor code using deprecated strncpy() interface to use strscpy()

Misc x86 cleanups.

The following commit deserves special mention:

   22dc02f81cddd Revert "sched/fair: Move unused stub functions to header"

This is in x86/cleanups, because the revert is a re-application of a
number of cleanups that got removed inadvertedly.

 Thanks,

	Ingo

------------------>
Arnd Bergmann (7):
      x86/cpu: Fix amd_check_microcode() declaration
      x86/apic: Hide unused safe_smp_processor_id() on 32-bit UP
      x86/asm: Avoid unneeded __div64_32 function definition
      x86/purgatory: Include header for warn() declaration
      x86/alternative: Add a __alt_reloc_selftest() prototype
      x86/paravirt: Silence unused native_pv_lock_init() function warning
      x86/qspinlock-paravirt: Fix missing-prototype warning

Justin Stitt (3):
      x86/platform/uv: Refactor code using deprecated strcpy()/strncpy() interfaces to use strscpy()
      x86/hpet: Refactor code using deprecated strncpy() interface to use strscpy()
      x86/platform/uv: Refactor code using deprecated strncpy() interface to use strscpy()

Peter Zijlstra (1):
      Revert "sched/fair: Move unused stub functions to header"


 arch/x86/boot/compressed/error.c          |  2 +-
 arch/x86/boot/compressed/error.h          |  2 +-
 arch/x86/include/asm/div64.h              |  6 ++++++
 arch/x86/include/asm/microcode_amd.h      |  3 +--
 arch/x86/include/asm/paravirt.h           |  7 +++++++
 arch/x86/include/asm/processor.h          |  2 ++
 arch/x86/include/asm/qspinlock.h          |  7 +------
 arch/x86/include/asm/qspinlock_paravirt.h |  2 ++
 arch/x86/kernel/alternative.c             |  1 +
 arch/x86/kernel/apic/ipi.c                |  2 ++
 arch/x86/kernel/apic/x2apic_uv_x.c        |  5 ++---
 arch/x86/kernel/hpet.c                    |  2 +-
 arch/x86/kernel/paravirt.c                |  3 ++-
 arch/x86/platform/uv/uv_nmi.c             | 12 ++++--------
 arch/x86/purgatory/purgatory.c            |  1 +
 kernel/locking/qspinlock_paravirt.h       | 20 ++++++++++----------
 kernel/sched/fair.c                       |  6 +++---
 kernel/sched/sched.h                      |  2 ++
 18 files changed, 49 insertions(+), 36 deletions(-)

             reply	other threads:[~2023-08-28 21:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-28 21:16 Ingo Molnar [this message]
2023-08-29  0:23 ` [GIT PULL] x86/cleanups for v6.6 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=ZO0OuPfs0bMddVTW@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --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