public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"bp@amd64.org" <bp@amd64.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"linux-tip-commits@vger.kernel.org" 
	<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:x86/urgent] x86, amd-nb: Rename CPU PCI id define for F4
Date: Thu, 31 Mar 2011 18:28:18 +0200	[thread overview]
Message-ID: <20110331162818.GC9350@aftab> (raw)
In-Reply-To: <20110331091401.64f2c81c@jbarnes-desktop>

On Thu, Mar 31, 2011 at 12:14:01PM -0400, Jesse Barnes wrote:
> > The new ID went upstream via cb293250c71f in the merge window, so i wanted to 
> > shorten the life-time of the obsoleted name - that will also reduce the chance 
> > of any conflicts.
> 
> Sounds good, thanks.

Yep, definitely a good idea since I have a couple of patches coming up
for the next merge window and they use this particular #define. That's
why I sent it out now, thinking it is trivial enough to go in and thus
to avoid conflicts at merge window time.

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-03-31 16:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 18:34 [PATCH] x86, amd-nb: Rename CPU PCI id define for F4 Borislav Petkov
2011-03-31  7:04 ` [tip:x86/urgent] " tip-bot for Borislav Petkov
2011-03-31 16:00   ` Jesse Barnes
2011-03-31 16:05     ` Ingo Molnar
2011-03-31 16:14       ` Jesse Barnes
2011-03-31 16:28         ` Borislav Petkov [this message]

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=20110331162818.GC9350@aftab \
    --to=bp@amd64.org \
    --cc=hpa@zytor.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --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