From: "H. Peter Anvin" <hpa@zytor.com>
To: Mike Travis <travis@sgi.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] x86: SGI UV3 Kernel Updates
Date: Wed, 06 Feb 2013 14:22:56 -0800 [thread overview]
Message-ID: <5112D7C0.7080009@zytor.com> (raw)
In-Reply-To: <20130205222648.204965172@gulag1.americas.sgi.com>
On 02/05/2013 02:26 PM, Mike Travis wrote:
> Kernel updates for SGI Ultraviolet system 3 (UV3)
>
> The new MMR definitions are added, and then the updates
> to each module are applied. Afterwards, a "trim" patch
> reduces the size of the MMR definitions file by about
> a third. This keeps "bi-sectability" in place.
>
Can you please re-send this with proper formatting? For one thing, all
your descriptions are indented.
-hpa
next prev parent reply other threads:[~2013-02-06 22:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 22:26 [PATCH 0/7] x86: SGI UV3 Kernel Updates Mike Travis
2013-02-05 22:26 ` [PATCH 1/7] x86, UV: UV3 Update MMR register definitions Mike Travis
2013-02-05 22:26 ` [PATCH 2/7] x86, UV: UV3 Update ACPI Check Mike Travis
2013-02-05 22:26 ` [PATCH 3/7] x86: UV3 Update Hub Info Mike Travis
2013-02-05 22:26 ` [PATCH 4/7] x86, UV: UV3 Update x2apic Support Mike Travis
2013-02-06 11:13 ` Ingo Molnar
2013-02-06 20:43 ` Mike Travis
2013-02-05 22:26 ` [PATCH 5/7] x86, UV: UV3 Update Time Support Mike Travis
2013-02-05 22:26 ` [PATCH 6/7] x86, UV: UV3 Check current gru hub support Mike Travis
2013-02-05 22:26 ` [PATCH 7/7] x86, UV: UV3 Trim MMR register definitions after code changes Mike Travis
2013-02-06 22:22 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-08 18:43 [PATCH 0/7] x86: SGI UV3 Kernel Updates Mike Travis
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=5112D7C0.7080009@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--cc=x86@kernel.org \
/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.