From: Matt Fleming <matt@console-pimps.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Robert Richter <robert.richter@amd.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Matt Helsley <matthltc@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: manual merge of the oprofile tree with the tip tree
Date: Tue, 12 Oct 2010 13:51:26 +0100 [thread overview]
Message-ID: <20101012125126.GE12335@console-pimps.org> (raw)
In-Reply-To: <20101012232349.938f83c0.sfr@canb.auug.org.au>
On Tue, Oct 12, 2010 at 11:23:49PM +1100, Stephen Rothwell wrote:
> Hi Matt,
>
> On Tue, 12 Oct 2010 07:03:27 +0100 Matt Fleming <matt@console-pimps.org> wrote:
> >
> > > return 0;
> > >
> > > pevent = perf_event_create_kernel_counter(&counter_config[event].attr,
> > > - cpu, -1,
> > > + cpu, NULL1,
> > > op_overflow_handler);
> >
> > Is that a typo? Shouldn't that be NULL, and not NULL1?
>
> Yes, its a typo in my patch :-( . I will fix it for tomorrow. Sorry about that.
Not a problem! Thanks
next prev parent reply other threads:[~2010-10-12 12:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 2:18 linux-next: manual merge of the oprofile tree with the tip tree Stephen Rothwell
2010-10-12 6:03 ` Matt Fleming
2010-10-12 12:23 ` Stephen Rothwell
2010-10-12 12:51 ` Matt Fleming [this message]
2010-10-15 12:43 ` Robert Richter
-- strict thread matches above, loose matches on Subject: below --
2012-03-21 5:31 Stephen Rothwell
2012-03-21 12:33 ` Robert Richter
2012-03-21 12:33 ` Robert Richter
2012-03-21 13:52 ` Stephen Rothwell
2012-03-21 13:52 ` Stephen Rothwell
2012-03-13 6:37 Stephen Rothwell
2012-03-13 8:31 ` Ingo Molnar
2010-10-12 2:13 Stephen Rothwell
2010-10-01 3:53 Stephen Rothwell
2010-10-01 13:21 ` Robert Richter
2010-10-01 13:21 ` Robert Richter
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=20101012125126.GE12335@console-pimps.org \
--to=matt@console-pimps.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matthltc@us.ibm.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.com \
--cc=sfr@canb.auug.org.au \
--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.