mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Quchaosheng <quchaosheng000406@163.com>,
	Shrikanth Hegde <sshegde@linux.ibm.com>
Subject: linux-next: manual merge of the tip tree with the jc_docs tree
Date: Mon, 28 Sep 2026 14:58:51 +0100	[thread overview]
Message-ID: <arpymyOST1apXE25@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]

Hi all,

Today's linux-next merge of the tip tree got a conflict in:

  Documentation/scheduler/index.rst

between commit:

  80c2913d0a06c ("sched/doc: add a preemption model overview")

from the jc_docs tree and commit:

  06a49ef784acf ("sched/docs: Document cpu_preferred_mask and Preferred CPU concept")

from the tip tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

diff --cc Documentation/scheduler/index.rst
index d6d75421756ac,a43647b9706d9..0000000000000
--- a/Documentation/scheduler/index.rst
+++ b/Documentation/scheduler/index.rst
@@@ -23,6 -23,6 +23,7 @@@ Schedule
      sched-stats
      sched-ext
      sched-debug
+     sched-paravirt
 +    sched-preemption
  
      text_files

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2026-09-28 13:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 13:58 Mark Brown [this message]
2026-09-28 14:03 ` Jonathan Corbet
2026-09-28 14:15 ` Shrikanth Hegde
2026-09-28 15:06   ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2022-04-19  1:55 Stephen Rothwell
2021-06-03  4:04 Stephen Rothwell
2020-12-04  4:38 Stephen Rothwell
2018-03-14  2:58 Stephen Rothwell
2017-06-21  4:18 Stephen Rothwell
2017-07-03  1:33 ` Stephen Rothwell

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=arpymyOST1apXE25@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=quchaosheng000406@163.com \
    --cc=sshegde@linux.ibm.com \
    --cc=tglx@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®