From: Jonathan Corbet <corbet@lwn.net>
To: Eric Engestrom <eric.engestrom@imgtec.com>
Cc: <linux-kernel@vger.kernel.org>, Jiri Kosina <trivial@kernel.org>,
<linux-doc@vger.kernel.org>
Subject: Re: [trivial PATCH] Documentation/sparse: fix typo
Date: Wed, 21 Mar 2018 09:18:19 -0600 [thread overview]
Message-ID: <20180321091819.3d519a2c@lwn.net> (raw)
In-Reply-To: <20180313111128.5803-1-eric.engestrom@imgtec.com>
On Tue, 13 Mar 2018 11:10:58 +0000
Eric Engestrom <eric.engestrom@imgtec.com> wrote:
> If the function enters and exits without the lock held, acquiring and
> releasing the lock inside the function in a balanced way, no
> -annotation is needed. The tree annotations above are for cases where
> +annotation is needed. The three annotations above are for cases where
> sparse would otherwise report a context imbalance.
Applied to the docs tree, thanks.
jon
prev parent reply other threads:[~2018-03-21 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 11:10 [trivial PATCH] Documentation/sparse: fix typo Eric Engestrom
2018-03-21 15:18 ` Jonathan Corbet [this message]
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=20180321091819.3d519a2c@lwn.net \
--to=corbet@lwn.net \
--cc=eric.engestrom@imgtec.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.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;
as well as URLs for NNTP newsgroup(s).