From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Borislav Petkov <borislav.petkov@amd.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Hans Rosenfeld <hans.rosenfeld@amd.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: linux-next: manual merge of the edac-amd tree with the tip tree
Date: Fri, 11 Feb 2011 14:28:35 +1100 [thread overview]
Message-ID: <20110211142835.5ef24abe.sfr@canb.auug.org.au> (raw)
Hi Borislav,
Today's linux-next merge of the edac-amd tree got a conflict in
include/linux/pci_ids.h between commit
41b2610c3443e6c4760e61fc10eef73f96f9f6a5 ("x86, amd: Extend AMD
northbridge caching code to support "Link Control" devices") from the tip
tree and commit 3d019f87099415f5f0a2f75b6f828db17e6e9445 ("PCI: Rename
CPU PCI id define") from the edac-amd tree.
Just context changes. I fixed it up (see below) and can carry the fix as
necessary.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
diff --cc include/linux/pci_ids.h
index 5aaf45e,5411e7b..0000000
--- a/include/linux/pci_ids.h
+++ b/include/linux/pci_ids.h
@@@ -517,8 -517,7 +517,8 @@@
#define PCI_DEVICE_ID_AMD_11H_NB_DRAM 0x1302
#define PCI_DEVICE_ID_AMD_11H_NB_MISC 0x1303
#define PCI_DEVICE_ID_AMD_11H_NB_LINK 0x1304
- #define PCI_DEVICE_ID_AMD_15H_NB_MISC 0x1603
+ #define PCI_DEVICE_ID_AMD_15H_NB_F3 0x1603
+#define PCI_DEVICE_ID_AMD_15H_NB_LINK 0x1604
#define PCI_DEVICE_ID_AMD_CNB17H_F3 0x1703
#define PCI_DEVICE_ID_AMD_LANCE 0x2000
#define PCI_DEVICE_ID_AMD_LANCE_HOME 0x2001
next reply other threads:[~2011-02-11 3:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 3:28 Stephen Rothwell [this message]
2011-02-11 8:47 ` linux-next: manual merge of the edac-amd tree with the tip tree Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2015-06-04 6:55 Stephen Rothwell
2015-06-04 8:01 ` Borislav Petkov
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=20110211142835.5ef24abe.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=borislav.petkov@amd.com \
--cc=hans.rosenfeld@amd.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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