public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Bjorn Helgaas" <bhelgaas@google.com>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
	Qiang Yu <qiang.yu@oss.qualcomm.com>,
	Wenbin Yao <wenbin.yao@oss.qualcomm.com>
Subject: linux-next: manual merge of the pci tree with the pci-current tree
Date: Mon, 5 Jan 2026 11:55:54 +1100	[thread overview]
Message-ID: <20260105115554.1afe97ce@canb.auug.org.au> (raw)

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

Hi all,

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

  drivers/pci/controller/dwc/pcie-qcom.c

between commit:

  0cc13256b605 ("PCI: qcom: Remove ASPM L0s support for MSM8996 SoC")

from the pci-current tree and commits:

  7c29cd0fdc07 ("PCI: qcom: Remove MSI-X Capability for Root Ports")
  6a1394990902 ("PCI: qcom: Remove DPC Extended Capability")

from the pci tree.

I fixed it up (I think - 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 drivers/pci/controller/dwc/pcie-qcom.c
index 5a318487b2b3,9b7cffc891d3..000000000000
--- a/drivers/pci/controller/dwc/pcie-qcom.c
+++ b/drivers/pci/controller/dwc/pcie-qcom.c
@@@ -1315,8 -1317,9 +1316,11 @@@ static int qcom_pcie_host_init(struct d
  			goto err_disable_phy;
  	}
  
 +	qcom_pcie_clear_aspm_l0s(pcie->pci);
 +
+ 	dw_pcie_remove_capability(pcie->pci, PCI_CAP_ID_MSIX);
+ 	dw_pcie_remove_ext_capability(pcie->pci, PCI_EXT_CAP_ID_DPC);
+ 
  	qcom_ep_reset_deassert(pcie);
  
  	if (pcie->cfg->ops->config_sid) {

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

             reply	other threads:[~2026-01-05  0:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05  0:55 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-24  0:25 linux-next: manual merge of the pci tree with the pci-current tree Stephen Rothwell
2024-10-24  6:56 ` Bartosz Golaszewski
2024-10-24 18:50   ` Bjorn Helgaas
2024-06-03  0:24 Stephen Rothwell
2018-08-01  0:42 Stephen Rothwell
2016-02-24  0:02 Stephen Rothwell
2014-03-12 13:00 Mark Brown
2010-03-26  0:57 Stephen Rothwell
2010-03-26  2:10 ` Jesse Barnes
2010-03-26  2:48   ` Stephen Rothwell
2010-03-26 16:03     ` Jesse Barnes
2010-03-26 14:43 ` Bjorn Helgaas
2009-02-06  2:50 Stephen Rothwell
2009-02-06 17:09 ` Jesse Barnes
2009-02-06 23:49   ` Rafael J. Wysocki
2009-02-07  0:07   ` Stephen Rothwell

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=20260105115554.1afe97ce@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=bhelgaas@google.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=manivannan.sadhasivam@oss.qualcomm.com \
    --cc=qiang.yu@oss.qualcomm.com \
    --cc=wenbin.yao@oss.qualcomm.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