mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Dave Airlie <airlied@redhat.com>, DRI <dri-devel@lists.freedesktop.org>
Cc: Alexey Minnekhanov <alexeymin@minlexx.ru>,
	Conor Dooley <conor.dooley@microchip.com>,
	Jia Wang <wangjia@ultrarisc.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>
Subject: linux-next: manual merge of the drm tree with the riscv-dt tree
Date: Fri, 13 Nov 2026 16:07:26 +0000	[thread overview]
Message-ID: <avc1vpWDQ7V0vcRc@sirena.org.uk> (raw)

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

Hi all,

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

  Documentation/devicetree/bindings/vendor-prefixes.yaml

between commit:

  f61b65abc9f41 ("dt-bindings: vendor-prefixes: Add shenrongda")

from the riscv-dt tree and commit:

  b55dbe9011975 ("dt-bindings: vendor-prefixes: Add Shen Chao Optoelectronics")

from the drm 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/devicetree/bindings/vendor-prefixes.yaml
index bc1e6361c6941,7602034374d7f..0000000000000
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@@ -1529,8 -1527,8 +1531,10 @@@ patternProperties
      description: SGX Sensortech
    "^sharp,.*":
      description: Sharp Corporation
+   "^shenchao,.*":
+     description: Shen Chao Optoelectronics (Shenzhen) Co., Ltd.
 +  "^shenrongda,.*":
 +    description: Shenzhen Rongda Computer Co., Ltd.
    "^shift,.*":
      description: SHIFT GmbH
    "^shimafuji,.*":

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

                 reply	other threads:[~2026-11-13 16:07 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=avc1vpWDQ7V0vcRc@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=airlied@redhat.com \
    --cc=alexeymin@minlexx.ru \
    --cc=conor.dooley@microchip.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=wangjia@ultrarisc.com \
    /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®