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: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Nishanth Menon <nm@ti.com>
Subject: linux-next: manual merge of the tip tree with the ti tree
Date: Wed, 23 Sep 2026 15:33:45 +0200	[thread overview]
Message-ID: <arPVObYK7l38CvdP@sirena.co.uk> (raw)

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

Hi all,

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

  arch/arm64/configs/defconfig

between commit:

  e557da9b756db ("arm64: configs: defconfig: Convert TISCI to modules")

from the ti tree and commit:

  bd94bea7165be ("arm64: defconfig: Drop redundant Qualcomm irqchip entries")

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 arch/arm64/configs/defconfig
index c41e5d5dbc81a,978e00891dca8..0000000000000
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@@ -1753,10 -1743,8 +1753,8 @@@ CONFIG_PWM_VISCONTI=
  CONFIG_PWM_XILINX=m
  CONFIG_SL28CPLD_INTC=y
  CONFIG_XILINX_INTC=y
- CONFIG_QCOM_PDC=y
- CONFIG_QCOM_MPM=y
 -CONFIG_TI_SCI_INTR_IRQCHIP=y
 -CONFIG_TI_SCI_INTA_IRQCHIP=y
 +CONFIG_TI_SCI_INTR_IRQCHIP=m
 +CONFIG_TI_SCI_INTA_IRQCHIP=m
  CONFIG_RESET_GPIO=m
  CONFIG_RESET_IMX7=y
  CONFIG_RESET_QCOM_AOSS=y

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

             reply	other threads:[~2026-09-23 13:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 13:33 Mark Brown [this message]
2026-09-23 13:41 ` Nishanth Menon

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=arPVObYK7l38CvdP@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=hpa@zytor.com \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=nm@ti.com \
    --cc=peterz@infradead.org \
    --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®