From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Takashi Iwai" <tiwai@suse•de>,
"Bjorn Helgaas" <bhelgaas@google•com>,
"Lorenzo Pieralisi" <lpieralisi@kernel•org>,
"Krzysztof Wilczyński" <kw@linux•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Mike Pastore <mike@oobak•org>, Yanteng Si <siyanteng@loongson•cn>
Subject: linux-next: manual merge of the sound tree with the pci tree
Date: Thu, 8 Jun 2023 10:57:14 +1000 [thread overview]
Message-ID: <20230608105714.39ee3c3d@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
Hi all,
Today's linux-next merge of the sound tree got a conflict in:
include/linux/pci_ids.h
between commit:
0ac448e0d29d ("PCI: Delay after FLR of Solidigm P44 Pro NVMe")
from the pci tree and commit:
28bd137a3c8e ("ALSA: hda: Add Loongson LS7A HD-Audio support")
from the sound 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 include/linux/pci_ids.h
index 0f9cdc6195a1,c0c4ca8e2851..000000000000
--- a/include/linux/pci_ids.h
+++ b/include/linux/pci_ids.h
@@@ -158,8 -158,9 +158,11 @@@
#define PCI_VENDOR_ID_LOONGSON 0x0014
+ #define PCI_DEVICE_ID_LOONGSON_HDA 0x7a07
+ #define PCI_DEVICE_ID_LOONGSON_HDMI 0x7a37
+
+#define PCI_VENDOR_ID_SOLIDIGM 0x025e
+
#define PCI_VENDOR_ID_TTTECH 0x0357
#define PCI_DEVICE_ID_TTTECH_MC322 0x000a
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2023-06-08 0:57 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=20230608105714.39ee3c3d@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=bhelgaas@google$(echo .)com \
--cc=kw@linux$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lpieralisi@kernel$(echo .)org \
--cc=mike@oobak$(echo .)org \
--cc=siyanteng@loongson$(echo .)cn \
--cc=tiwai@suse$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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