From: "Ray Bryant" <raybry@mpdtxmail.amd.com>
To: "Xuekun Hu" <xuekun.hu@gmail.com>
Cc: linux-kernel@vger.kernel.org, raybry@mpdtxmail.amd.com,
akpm@osdl.org, hawkes@sgi.com
Subject: Re: lockmeter: fix lock counter roll over issue
Date: Mon, 15 Aug 2005 09:16:53 -0500 [thread overview]
Message-ID: <200508150916.54276.raybry@mpdtxmail.amd.com> (raw)
In-Reply-To: <398d69300508150035246230af@mail.gmail.com>
On Monday 15 August 2005 02:35, Xuekun Hu wrote:
> Does anyone have inputs?
>
Xuekun ,
I was on vacation last week. I just saw your patch yesterday. It looks
reasonable, but I will test it later today.
You should also cc John Hawkes (hawkes@sgi.com).
Also, please note my email address change: my current email address is
raybry@mpdtxmail.amd.com.
Andrew is not so much interested in these changes as the lockmeter patch is
not in -mm.
--
Ray Bryant
AMD Performance Labs Austin, Tx
512-602-0038 (o) 512-507-7807 (c)
next prev parent reply other threads:[~2005-08-15 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 4:00 lockmeter: fix lock counter roll over issue Xuekun Hu
2005-08-15 7:35 ` Xuekun Hu
2005-08-15 14:16 ` Ray Bryant [this message]
2005-08-18 12:41 ` Xuekun Hu
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=200508150916.54276.raybry@mpdtxmail.amd.com \
--to=raybry@mpdtxmail.amd.com \
--cc=akpm@osdl.org \
--cc=hawkes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xuekun.hu@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