From: "H.J. Lu" <hjl.tools@gmail.com>
To: Quentin Neill <quentin.neill.gnu@gmail.com>
Cc: Jan Beulich <JBeulich@novell.com>, binutils@sourceware.org
Subject: Re: [PATCH] add bdver2 processor.
Date: Thu, 12 May 2011 02:34:00 -0000 [thread overview]
Message-ID: <BANLkTik3NXE+3po-qh7gVWYLKTQVmZFxZA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimpu2+Y5bojA1RJydfgtuZcMPvFaQ@mail.gmail.com>
On Wed, May 11, 2011 at 7:16 PM, Quentin Neill
<quentin.neill.gnu@gmail.com> wrote:
> On Wed, May 11, 2011 at 9:24 AM, Quentin Neill
> <quentin.neill.gnu@gmail.com> wrote:
>> On Wed, May 11, 2011 at 1:40 AM, Jan Beulich <JBeulich@novell.com> wrote:
>>>>>> On 10.05.11 at 21:10, "H.J. Lu" <hjl.tools@gmail.com> wrote:
>>>> On Tue, May 10, 2011 at 11:28 AM, Quentin Neill
>>>>> Should I rename the PROCESSOR_BDVER1 variable to perhaps PROCESSOR_BDVER?
>>>>
>>>> Sounds good to me.
>>>
>>> And in a couple of years from now nobody will be able to tell what the
>>> "VER" in the name stands for ...
>>>
>>> Jan
>>
>> I thought of that last night when I got home.
>>
>> I'll change it to PROCESSOR_BD with another patch.
>> --
>> Quentin
>
> So attached is the tested PROCESSOR_BD variable rename patch, which
> passes "make check" in x86_64.
>
> Okay to commit?
OK.
--
H.J.
prev parent reply other threads:[~2011-05-12 2:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 16:16 Quentin Neill
2011-05-04 16:45 ` H.J. Lu
[not found] ` <BANLkTinukDoLD-yJ6SyfDbAjLO=NvHiN2w@mail.gmail.com>
[not found] ` <BANLkTinNnuhwjwp_0+FubD4=wzSixt6XvA@mail.gmail.com>
2011-05-10 16:52 ` Quentin Neill
2011-05-10 17:56 ` H.J. Lu
2011-05-10 18:28 ` Quentin Neill
2011-05-10 19:11 ` H.J. Lu
2011-05-10 20:12 ` Quentin Neill
2011-05-10 21:15 ` H.J. Lu
2011-05-11 6:40 ` Jan Beulich
2011-05-11 14:24 ` Quentin Neill
2011-05-12 2:17 ` Quentin Neill
2011-05-12 2:34 ` H.J. Lu [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=BANLkTik3NXE+3po-qh7gVWYLKTQVmZFxZA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=JBeulich@novell.com \
--cc=binutils@sourceware.org \
--cc=quentin.neill.gnu@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).