From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Anup Patel <anup@brainfault•org>
Cc: Andrew Jones <ajones@ventanamicro•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
"Paul E. McKenney" <paulmck@kernel•org>
Subject: linux-next: manual merge of the kvm-riscv tree with the rcu tree
Date: Tue, 2 Jan 2024 13:00:03 +1100 [thread overview]
Message-ID: <20240102130003.09d52290@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2120 bytes --]
Hi all,
FIXME: Add owner of second tree to To:
Add author(s)/SOB of conflicting commits.
Today's linux-next merge of the kvm-riscv tree got a conflict in:
Documentation/admin-guide/kernel-parameters.txt
between commit:
801f246637ed ("doc: Add EARLY flag to early-parsed kernel boot parameters")
from the rcu tree and commit:
323925ed6dbb ("RISC-V: paravirt: Add skeleton for pv-time support")
from the kvm-riscv 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.
--
Cheers,
Stephen Rothwell
diff --cc Documentation/admin-guide/kernel-parameters.txt
index cfeea158a4c6,a0d9259e4857..000000000000
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@@ -4000,15 -3980,14 +4000,15 @@@
(bounds check bypass). With this option data leaks are
possible in the system.
- nospectre_v2 [X86,PPC_E500,ARM64] Disable all mitigations for
- the Spectre variant 2 (indirect branch prediction)
- vulnerability. System may allow data leaks with this
- option.
+ nospectre_v2 [X86,PPC_E500,ARM64,EARLY] Disable all mitigations
+ for the Spectre variant 2 (indirect branch
+ prediction) vulnerability. System may allow data
+ leaks with this option.
- no-steal-acc [X86,PV_OPS,ARM64,PPC/PSERIES,EARLY] Disable
- no-steal-acc [X86,PV_OPS,ARM64,PPC/PSERIES,RISCV] Disable
- paravirtualized steal time accounting. steal time is
- computed, but won't influence scheduler behaviour
++ no-steal-acc [X86,PV_OPS,ARM64,PPC/PSERIES,RISCV,EARLY] Disable
+ paravirtualized steal time accounting. steal
+ time is computed, but won't influence scheduler
+ behaviour
nosync [HW,M68K] Disables sync negotiation for all devices.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2024-01-02 2:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240102130003.09d52290@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=ajones@ventanamicro$(echo .)com \
--cc=anup@brainfault$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paulmck@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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