From: Olof Johansson <olof@lixom.net>
To: paulus@samba.org
Cc: linuxppc-dev@ozlabs.org, gregkh@suse.de
Subject: [PATCH] [0/4] PMC-related cleanups [v2]
Date: Sun, 28 Jan 2007 21:21:43 -0600 [thread overview]
Message-ID: <20070129032143.GC6412@lixom.net> (raw)
The following short series contains a few patches to abstract and clean
up some of the PMC handling on powerpc, followed by the introduction of
the sysfs support for PMCs on PA6T.
Edits since last submit:
* Setting .owner in the sysdev_attr patch
* Using intvec_top instead of intvec_base for setting "soft" vectors
* Fix patch badness with duplicate .pmc_type for one entry
Thanks,
Olof
next reply other threads:[~2007-01-29 3:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 3:21 Olof Johansson [this message]
2007-01-29 3:23 ` [PATCH] [1/4] powerpc: Oprofile cleanup [v2] Olof Johansson
2007-01-29 3:23 ` [PATCH] [2/4] powerpc: Add PMC type to cputable [v2] Olof Johansson
2007-01-29 3:24 ` [PATCH] [3/4] Introduce _SYSDEV_ATTR Olof Johansson
2007-01-29 3:25 ` [PATCH] [4/4] powerpc: PA6T PMC support [v2] Olof Johansson
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=20070129032143.GC6412@lixom.net \
--to=olof@lixom.net \
--cc=gregkh@suse.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).