From: Christoph Hellwig <hch@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: Move perfmon tables from thread_struct to pfm_context
Date: Tue, 29 Aug 2006 19:55:28 +0000 [thread overview]
Message-ID: <20060829195528.GA17616@infradead.org> (raw)
In-Reply-To: <20060829110856.A23515@unix-os.sc.intel.com>
On Tue, Aug 29, 2006 at 11:08:56AM -0700, Keshavamurthy Anil S wrote:
> This patch renders thread_struct->pmcs[] and thread_struct->pmds[]
> OBSOLETE. The actual table is moved to pfm_context structure which
> is the right thing to do. Also this will in future avoid KABI breakages
> for the distro as well when the table size changes.
NACK. There is no such thing as a KABI, and any patch the claims to
help towards it will automatically be rejected. You should get a doctor
to help you stop seeing things like that.
next prev parent reply other threads:[~2006-08-29 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 18:08 Move perfmon tables from thread_struct to pfm_context Keshavamurthy Anil S
2006-08-29 19:55 ` Keshavamurthy Anil S
2006-08-29 19:55 ` Christoph Hellwig [this message]
2006-08-29 21:29 ` Stephane Eranian
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=20060829195528.GA17616@infradead.org \
--to=hch@infradead.org \
--cc=linux-ia64@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox