All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Rosenfeld, Hans" <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: Re: linux-next: manual merge of the edac-amd tree with the tip tree
Date: Fri, 11 Feb 2011 09:47:41 +0100	[thread overview]
Message-ID: <20110211084741.GA18661@aftab> (raw)
In-Reply-To: <20110211142835.5ef24abe.sfr@canb.auug.org.au>

Hey Stephen,

On Thu, Feb 10, 2011 at 10:28:35PM -0500, Stephen Rothwell wrote:
> 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

Yeah, we decided to call all CPU PCI devices on F15h and later simply by
their PCI function numbers for simplicity. I'll fix the .._LINK thing
when all the merging settles after .39-rc1.

Thanks.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2011-02-11  8:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11  3:28 linux-next: manual merge of the edac-amd tree with the tip tree Stephen Rothwell
2011-02-11  8:47 ` Borislav Petkov [this message]
  -- 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=20110211084741.GA18661@aftab \
    --to=bp@amd64.org \
    --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=sfr@canb.auug.org.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.