From: Robin Holt <holt@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Robin Holt <holt@sgi.com>,
tglx@linutronix.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Jack Steiner <steiner@sgi.com>,
Cliff Whickman <cpw@sgi.com>
Subject: Re: [patch 0/2] x86, UV: fixups for configurations with a large number of nodes.
Date: Fri, 16 Oct 2009 09:55:26 -0500 [thread overview]
Message-ID: <20091016145526.GA8903@sgi.com> (raw)
In-Reply-To: <20091016125313.GB15393@elte.hu>
On Fri, Oct 16, 2009 at 02:53:13PM +0200, Ingo Molnar wrote:
...
> So ... is the commit log message i've put into the commit below correct,
> or is it still only a cleanup patch? You really need to put that kind of
> info into your changelogs - it helps maintainers put it into the right
> kernel release.
>
> Ingo
...
> The open-coded code was wrong as well - it might explain a
> few of our unexplained bau hangs.
Terrific. Thank you for fixing up my commit message. I will try to be
more complete next time.
Robin
WARNING: multiple messages have this Message-ID (diff)
From: Robin Holt <holt@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Robin Holt <holt@sgi.com>,
tglx@linutronix.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Jack Steiner <steiner@sgi.com>,
Cliff Whickman <cpw@sgi.com>
Subject: Re: [patch 0/2] x86, UV: fixups for configurations with a large number of nodes.
Date: Fri, 16 Oct 2009 09:55:26 -0500 [thread overview]
Message-ID: <20091016145526.GA8903@sgi.com> (raw)
In-Reply-To: <20091016125313.GB15393@elte.hu>
On Fri, Oct 16, 2009 at 02:53:13PM +0200, Ingo Molnar wrote:
...
> So ... is the commit log message i've put into the commit below correct,
> or is it still only a cleanup patch? You really need to put that kind of
> info into your changelogs - it helps maintainers put it into the right
> kernel release.
>
> Ingo
...
> The open-coded code was wrong as well - it might explain a
> few of our unexplained bau hangs.
Terrific. Thank you for fixing up my commit message. I will try to be
more complete next time.
Robin
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-10-16 14:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 22:39 [patch 0/2] x86, UV: fixups for configurations with a large number of nodes Robin Holt
2009-10-15 22:39 ` Robin Holt
2009-10-15 22:40 ` [patch 1/2] x86, UV: Fix information in __uv_hub_info structure Robin Holt
2009-10-15 22:40 ` Robin Holt
2009-10-16 7:22 ` [tip:x86/urgent] " tip-bot for Robin Holt
2009-10-15 22:40 ` [patch 2/2] x86, UV: Modify bau to use uv_gpa_to_pnode() Robin Holt
2009-10-15 22:40 ` Robin Holt
2009-10-16 6:34 ` [patch 0/2] x86, UV: fixups for configurations with a large number of nodes Ingo Molnar
2009-10-16 6:34 ` Ingo Molnar
2009-10-16 11:29 ` Robin Holt
2009-10-16 11:29 ` Robin Holt
2009-10-16 12:53 ` Ingo Molnar
2009-10-16 12:53 ` Ingo Molnar
2009-10-16 14:55 ` Robin Holt [this message]
2009-10-16 14:55 ` Robin Holt
2009-10-16 12:56 ` [tip:x86/urgent] x86, UV: Fix and clean up bau code to use uv_gpa_to_pnode() tip-bot for Robin Holt
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=20091016145526.GA8903@sgi.com \
--to=holt@sgi.com \
--cc=cpw@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=steiner@sgi.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.