linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-um@lists.infradead.org,
	Richard Weinberger <richard@nod.at>,
	Anton Ivanov <anton.ivanov@cambridgegreys.com>
Subject: [GIT PULL] uml 6.18-rc1
Date: Mon,  6 Oct 2025 11:34:50 +0200	[thread overview]
Message-ID: <20251006093601.33082-3-johannes@sipsolutions.net> (raw)

Hi Linus,

UML doesn't have a lot of changes this time around, as you
can see in the diffstat and tag message below. I tested a
merged and booted it, there should be no conflicts.

Please pull and let us know if there's any problem.

Thanks,
johannes



The following changes since commit 76eeb9b8de9880ca38696b2fb56ac45ac0a25c6c:

  Linux 6.17-rc5 (2025-09-07 14:22:57 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/uml/linux.git tags/uml-for-linux-6.18-rc1

for you to fetch changes up to e66ae377fe219c98d3d5b8a0d35da4413a5390ca:

  um: Remove unused ipi_pipe field from cpuinfo_um (2025-09-10 14:23:58 +0200)

----------------------------------------------------------------
updates for UML, notably
 - minor preparations for SMP support
 - SPARSE_IRQ support for kunit
 - help output cleanups

----------------------------------------------------------------
Johannes Berg (1):
      um: virtio-pci: implement .shutdown()

Sinan Nalkaya (1):
      um: Support SPARSE_IRQ

Tiwei Bie (10):
      um: Add missing trailing newline to help messages
      um: vector: Fix indentation for help message
      um: Fix help message for ssl-non-raw
      um: Indent time-travel help messages
      um: Remove unused offset and child_err fields from stub_data
      um: Remove outdated comment about STUB_DATA_PAGES
      um: Centralize stub size calculations
      um: Stop tracking virtual CPUs via mm_cpumask()
      um: Remove unused cpu_data and current_cpu_data macros
      um: Remove unused ipi_pipe field from cpuinfo_um

 arch/um/Kconfig                         |  1 +
 arch/um/drivers/ssl.c                   |  5 ++++-
 arch/um/drivers/ubd_kern.c              |  2 +-
 arch/um/drivers/vector_kern.c           |  2 +-
 arch/um/drivers/virtio_pcidev.c         |  6 ++++++
 arch/um/include/asm/mmu_context.h       | 11 ----------
 arch/um/include/asm/processor-generic.h |  3 ---
 arch/um/include/shared/as-layout.h      |  5 +++--
 arch/um/include/shared/skas/stub-data.h |  3 +--
 arch/um/kernel/dtb.c                    |  2 +-
 arch/um/kernel/irq.c                    |  5 +++++
 arch/um/kernel/time.c                   | 37 +++++++++++++++++----------------
 arch/um/kernel/um_arch.c                |  7 +------
 arch/um/os-Linux/skas/process.c         |  2 +-
 arch/x86/um/shared/sysdep/stub_32.h     |  2 +-
 arch/x86/um/shared/sysdep/stub_64.h     |  2 +-
 16 files changed, 46 insertions(+), 49 deletions(-)


             reply	other threads:[~2025-10-06  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06  9:34 Johannes Berg [this message]
2025-10-06 21:00 ` [GIT PULL] uml 6.18-rc1 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=20251006093601.33082-3-johannes@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=richard@nod.at \
    --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;
as well as URLs for NNTP newsgroup(s).