From: Stephen Rothwell <sfr@canb.auug.org.au>
To: stephane eranian <eranian@googlemail.com>
Cc: linux-next@vger.kernel.org, paulus@samba.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: linux-next: concerns over the perfmon3 tree
Date: Wed, 26 Nov 2008 21:34:49 +1100 [thread overview]
Message-ID: <20081126213449.ab269449.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 329 bytes --]
Hi Stephane,
Given the concerns expressed by Ingo, I have dropped the perfmon3 tree
from linux-next until they have been addressed. Hopefully that will not
be loo long. Let us all know how we can help with this.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-11-26 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 10:34 Stephen Rothwell [this message]
2008-11-26 10:47 ` linux-next: concerns over the perfmon3 tree Ingo Molnar
2008-11-26 13:25 ` stephane eranian
2008-11-26 13:27 ` 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=20081126213449.ab269449.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=eranian@googlemail.com \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox