From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Randy Dunlap <rdunlap@infradead.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Jan 7 (rcutorture)
Date: Mon, 7 Jan 2013 15:47:32 -0800 [thread overview]
Message-ID: <20130107234732.GE2525@linux.vnet.ibm.com> (raw)
In-Reply-To: <1357601501.5190.14.camel@gandalf.local.home>
On Mon, Jan 07, 2013 at 06:31:41PM -0500, Steven Rostedt wrote:
> On Tue, 2013-01-08 at 10:24 +1100, Stephen Rothwell wrote:
>
> > > Stephen, can you send me the config that gave you that error.
> >
> > It was Randy and the config was in the mail the Paul cc'd you on.
> >
>
> Ah, I didn't read that far. I'm use to just cutting off Paul's emails
> short anyway. He never trims them ;-)
And if I had trimmed this one, I would have had to resend anyway. ;-)
Thanx, Paul
next prev parent reply other threads:[~2013-01-07 23:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 3:26 linux-next: Tree for Jan 7 Stephen Rothwell
2013-01-07 3:26 ` Stephen Rothwell
2013-01-07 19:42 ` linux-next: Tree for Jan 7 (rcutorture) Randy Dunlap
2013-01-07 22:16 ` Paul E. McKenney
2013-01-07 22:59 ` Stephen Rothwell
2013-01-07 23:12 ` Steven Rostedt
2013-01-07 23:24 ` Stephen Rothwell
2013-01-07 23:31 ` Steven Rostedt
2013-01-07 23:47 ` Paul E. McKenney [this message]
2013-01-08 0:36 ` Steven Rostedt
2013-01-08 3:53 ` Paul E. McKenney
2013-01-08 6:53 ` Randy Dunlap
2013-01-14 16:45 ` Randy Dunlap
2013-01-14 17:32 ` Paul E. McKenney
2013-01-14 18:49 ` Randy Dunlap
2013-01-14 19:49 ` Paul E. McKenney
2013-01-15 3:08 ` Steven Rostedt
2013-01-15 4:05 ` Paul E. McKenney
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=20130107234732.GE2525@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
/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.