Received-SPF: pass (google.com: domain of linux-kernel+bounces-13973-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Date: Tue, 2 Jan 2024 13:00:03 +1100
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
Message-ID: <20240102130003.09d52290@canb.auug.org.au>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/dyg0UfZdeGhEY2A+kyZH/IV";
 protocol="application/pgp-signature"; micalg=pgp-sha256

--Sig_/dyg0UfZdeGhEY2A+kyZH/IV
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

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.

--=20
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.
 =20
 -	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.
 =20
- 	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
 =20
  	nosync		[HW,M68K] Disables sync negotiation for all devices.
 =20

--Sig_/dyg0UfZdeGhEY2A+kyZH/IV
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmWTbiMACgkQAVBC80lX
0GyzLAgAi6+RTCnBgDWiBV21hyLu5jfsEDCOlbDnttME50/1OEL890nrnjcZdmOG
1imqG2KKR9mpxzkbQPjzrXlnl+FivHm3DAYAM6UmZBPZjIVHhOoM3OX5W2ZZKnEV
M63e7tcahietx44/DA63oAAszMdqUASd0clAZfEaPmbSR4T7z9evzH4+cUmeaBSU
5XTvVlfaoEE9lEAXZ85hRjaXylnxxjCz8wdBk+03Nq9a+Q+LE25xG8Y7tUPib57C
7neo0/xU2YvuPWd82ZztvzlPpi52B3S9hnd0JUx6SNCG1bghjaZNUrUwRW/tPySN
xkHRdaNqzuJkK1wfEnz0Iql5O69T8A==
=NXL0
-----END PGP SIGNATURE-----

--Sig_/dyg0UfZdeGhEY2A+kyZH/IV--