From: Peter Zijlstra <peterz@infradead.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Davidlohr Bueso <davidlohr@hp.com>,
mingo@kernel.org, jason.low2@hp.com, aswin@hp.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -tip v2 6/7] locking: Move docs into Documentation/locking/
Date: Thu, 31 Jul 2014 08:53:08 +0200 [thread overview]
Message-ID: <20140731065308.GL19379@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <53D95D68.1000402@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On Wed, Jul 30, 2014 at 02:02:32PM -0700, Randy Dunlap wrote:
> On 07/30/14 13:41, Davidlohr Bueso wrote:
> > Specifically:
> > Documentation/locking/lockdep-design.txt
> > Documentation/locking/lockstat.txt
> > Documentation/locking/mutex-design.txt
> > Documentation/locking/rt-mutex-design.txt
> > Documentation/locking/rt-mutex.txt
> > Documentation/locking/spinlocks.txt
> > Documentation/locking/ww-mutex-design.txt
> >
> > Signed-off-by: Davidlohr Bueso <davidlohr@hp.com>
>
> Did you read and use Documentation/SubmittingPatches? see:
Not in the last few years, covert changes to that file are likely to be
missed by everybody already doing kernel work for a living.
> Please use "git diff -M --stat --summary" to generate the diffstat:
> the -M enables rename detection, and the summary enables a summary of
> new/deleted or renamed files.
Pretty pointless as I'll pull the lot through quilt, which will destroy
any such niceties.
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-07-31 6:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 20:41 [PATCH -tip v2 1/7] locking/mutex: Standardize arguments in lock/unlock slowpaths Davidlohr Bueso
2014-07-30 20:41 ` [PATCH -tip v2 2/7] locking/mutex: Document quick lock release when unlocking Davidlohr Bueso
2014-08-13 10:55 ` [tip:locking/core] locking/mutexes: " tip-bot for Davidlohr Bueso
2014-07-30 20:41 ` [PATCH -tip v2 3/7] locking/mcs: Remove obsolete comment Davidlohr Bueso
2014-08-13 10:55 ` [tip:locking/core] " tip-bot for Davidlohr Bueso
2014-07-30 20:41 ` [PATCH -tip v2 4/7] locking/mutex: Refactor optimistic spinning code Davidlohr Bueso
2014-07-31 0:56 ` Jason Low
2014-08-13 10:55 ` [tip:locking/core] locking/mutexes: " tip-bot for Davidlohr Bueso
2014-07-30 20:41 ` [PATCH -tip v2 5/7] locking/mutex: Use MUTEX_SPIN_ON_OWNER when appropriate Davidlohr Bueso
2014-08-13 10:55 ` [tip:locking/core] locking/mutexes: " tip-bot for Davidlohr Bueso
2014-07-30 20:41 ` [PATCH -tip v2 6/7] locking: Move docs into Documentation/locking/ Davidlohr Bueso
2014-07-30 21:02 ` Randy Dunlap
2014-07-31 6:53 ` Peter Zijlstra [this message]
2014-08-13 10:56 ` [tip:locking/core] locking/Documentation: Move locking related " tip-bot for Davidlohr Bueso
2014-07-30 20:41 ` [PATCH -tip v2 7/7] Documentation: Update locking/mutex-design.txt disadvantages Davidlohr Bueso
2014-08-13 10:56 ` [tip:locking/core] locking/Documentation: Update locking/ mutex-design.txt disadvantages tip-bot for Davidlohr Bueso
2014-08-13 10:54 ` [tip:locking/core] locking/mutexes: Standardize arguments in lock /unlock slowpaths tip-bot for Davidlohr Bueso
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=20140731065308.GL19379@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=aswin@hp.com \
--cc=davidlohr@hp.com \
--cc=jason.low2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rdunlap@infradead.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