From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Juri Lelli <juri.lelli@gmail.com>,
linux-kernel@vger.kernel.org, Yong Zhang <yong.zhang0@gmail.com>
Subject: Re: [PATCH] Documentation: statistics about nested locks
Date: Mon, 16 May 2011 12:35:59 +0200 [thread overview]
Message-ID: <20110516103559.GA19837@elte.hu> (raw)
In-Reply-To: <1305540776.2466.4094.camel@twins>
* Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> On Mon, 2011-05-16 at 12:01 +0200, Juri Lelli wrote:
> > +The graph below shows the relation between the lock functions and the
> > various
> > +hooks therein.
>
> That smells like the patch has whitespace damage..
Yeah, Documentation/email-clients.txt might help there.
Thanks,
Ingo
next prev parent reply other threads:[~2011-05-16 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 10:01 [PATCH] Documentation: statistics about nested locks Juri Lelli
2011-05-16 10:12 ` Peter Zijlstra
2011-05-16 10:35 ` Ingo Molnar [this message]
2011-05-17 8:39 ` Juri Lelli
2011-05-17 8:47 ` Yong Zhang
2011-05-17 2:00 ` Yong Zhang
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=20110516103559.GA19837@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yong.zhang0@gmail.com \
/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