From: Ingo Molnar <mingo@elte.hu>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
bp@amd64.org, tglx@linutronix.de, borislav.petkov@amd.com,
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:05:52 +0200 [thread overview]
Message-ID: <20110331160552.GD9827@elte.hu> (raw)
In-Reply-To: <20110331090039.12358ee6@jbarnes-desktop>
* Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> On Thu, 31 Mar 2011 07:04:41 GMT
> tip-bot for Borislav Petkov <bp@amd64.org> wrote:
>
> > Commit-ID: cb6c8520f6f6bba7b7e1a6de3360a8edfd8243b6
> > Gitweb: http://git.kernel.org/tip/cb6c8520f6f6bba7b7e1a6de3360a8edfd8243b6
> > Author: Borislav Petkov <bp@amd64.org>
> > AuthorDate: Wed, 30 Mar 2011 20:34:47 +0200
> > Committer: Ingo Molnar <mingo@elte.hu>
> > CommitDate: Thu, 31 Mar 2011 08:51:38 +0200
> >
> > x86, amd-nb: Rename CPU PCI id define for F4
> >
> > With increasing number of PCI function ids, add the PCI function
> > id in the define name instead of its symbolic name in the BKDG
> > for more clarity. This renames function 4 define.
> >
>
> I guess I don't see how a rename is urgent, but you can add my
> Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org>
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.
Thanks,
Ingo
next prev parent reply other threads:[~2011-03-31 16:06 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 [this message]
2011-03-31 16:14 ` Jesse Barnes
2011-03-31 16:28 ` 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=20110331160552.GD9827@elte.hu \
--to=mingo@elte.hu \
--cc=borislav.petkov@amd.com \
--cc=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@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 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.