mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@redhat.com>
To: peterz@infradead.org, mingo@redhat.com, corbet@lwn.net
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	juri.lelli@redhat.com
Subject: [PATCH 0/2] Update lockdep doc and add section about annotations
Date: Tue, 13 Feb 2018 19:55:17 +0100	[thread overview]
Message-ID: <20180213185519.18186-1-juri.lelli@redhat.com> (raw)

Hi,

a couple of patches to lockdep docs.

First one is a small fix for that fact that Peter made documentation
stale (as usual :P).

Second one is an RFC. I thought that adding some info about lockdep
asserts might help spread adoption even wider (mostly regarding
lockdep_pin_lock stuff, which is pretty new and maybe got unnoticed
outside of the scheduler?).

Best,

- Juri 

Juri Lelli (2):
  Documentation/locking/lockdep: update info about states
  Documentation/locking/lockdep: Add section about available annotations

 Documentation/locking/lockdep-design.txt | 51 ++++++++++++++++++++++++++++++--
 1 file changed, 49 insertions(+), 2 deletions(-)

-- 
2.14.3

             reply	other threads:[~2018-02-13 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13 18:55 Juri Lelli [this message]
2018-02-13 18:55 ` [PATCH 1/2] Documentation/locking/lockdep: update info about states Juri Lelli
2018-02-14 11:04   ` [tip:locking/core] Documentation/locking/lockdep: Update " tip-bot for Juri Lelli
2018-02-13 18:55 ` [RFC PATCH 2/2] Documentation/locking/lockdep: Add section about available annotations Juri Lelli
2018-02-14 11:04   ` [tip:locking/core] " tip-bot for Juri Lelli
2018-02-14  9:44 ` [PATCH 0/2] Update lockdep doc and add section about annotations Peter Zijlstra

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=20180213185519.18186-1-juri.lelli@redhat.com \
    --to=juri.lelli@redhat.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@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
all inboxes | Powered by JetHome®