Linux-Next discussions
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>,
	Wireless <linux-wireless@vger.kernel.org>
Cc: Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Ping-Ke Shih <pkshih@realtek.com>, Will Deacon <will@kernel.org>,
	Yicong Yang <yang.yicong@picoheart.com>
Subject: linux-next: manual merge of the wireless-next tree with the arm64 tree
Date: Mon, 3 Aug 2026 15:04:13 +0100	[thread overview]
Message-ID: <anCf3WnRSrf3VD7I@sirena.org.uk> (raw)

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

Hi all,

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

  include/linux/pci_ids.h

between commit:

  cf65b4d765b5f ("perf/dwc_pcie: Add support for Picoheart vendor devices")

from the arm64 tree and commit:

  888b1934642b7 ("PCI: Move Spacemit vendor and device IDs to linux/pci_ids.h")

from the wireless-next 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 include/linux/pci_ids.h
index b0aad3af268b6,d6f26cacc8e35..0000000000000
--- a/include/linux/pci_ids.h
+++ b/include/linux/pci_ids.h
@@@ -2640,8 -2640,10 +2640,12 @@@
  #define PCI_VENDOR_ID_SUNIX		0x1fd4
  #define PCI_DEVICE_ID_SUNIX_1999	0x1999
  
+ #define PCI_VENDOR_ID_SPACEMIT		0x201f
+ #define PCI_DEVICE_ID_SPACEMIT_K1	0x0001
+ #define PCI_DEVICE_ID_SPACEMIT_K3	0x0002
+ 
 +#define PCI_VENDOR_ID_PICOHEART		0x20fa
 +
  #define PCI_VENDOR_ID_HINT             0x3388
  #define PCI_DEVICE_ID_HINT_VXPROII_IDE 0x8013
  

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

                 reply	other threads:[~2026-08-03 14:04 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=anCf3WnRSrf3VD7I@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=asrinivasan@oss.tenstorrent.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=will@kernel.org \
    --cc=yang.yicong@picoheart.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