From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alex Deucher <alexdeucher@gmail.com>, Jonathan Corbet <corbet@lwn.net>
Cc: Hans de Goede <hdegoede@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Ma Jun <Jun.Ma2@amd.com>, Sumit Garg <sumit.garg@linaro.org>
Subject: linux-next: manual merge of the amdgpu tree with the jc_docs tree
Date: Tue, 12 Dec 2023 10:46:57 +1100 [thread overview]
Message-ID: <20231212104657.524d359e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
Hi all,
Today's linux-next merge of the amdgpu tree got a conflict in:
Documentation/driver-api/index.rst
between commit:
50709576d81b ("Documentation: Destage TEE subsystem documentation")
from the jc_docs tree and commit:
2128f3cca5a2 ("Documentation/driver-api: Add document about WBRF mechanism")
from the amdgpu 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/driver-api/index.rst
index 9511db303446,8bc4ebe7a36f..000000000000
--- a/Documentation/driver-api/index.rst
+++ b/Documentation/driver-api/index.rst
@@@ -112,7 -115,7 +112,8 @@@ available subsections can be seen below
hte/index
wmi
dpll
+ tee
+ wbrf
.. only:: subproject and html
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-12-11 23:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 23:46 Stephen Rothwell [this message]
2023-12-11 23:58 ` linux-next: manual merge of the amdgpu tree with the jc_docs tree Jonathan Corbet
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=20231212104657.524d359e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Jun.Ma2@amd.com \
--cc=alexdeucher@gmail.com \
--cc=corbet@lwn.net \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sumit.garg@linaro.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