From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] rcu: doc: update example about stale data
Date: Sun, 28 Oct 2018 10:29:18 -0700 [thread overview]
Message-ID: <20181028172918.GO4170@linux.ibm.com> (raw)
In-Reply-To: <CAEXW_YTCJS9Yxt4J=nbF+Omdon_4Li2BUiVzALGX246fMA9J2Q@mail.gmail.com>
On Sat, Oct 27, 2018 at 09:44:31PM -0700, Joel Fernandes wrote:
> On Sat, Oct 27, 2018 at 7:16 PM, Joel Fernandes (Google)
> <joel@joelfernandes.org> wrote:
> > The RCU example for 'rejecting stale data' on system-call auditting
> > stops iterating through the rules if a deleted one is found. It makes
> > more sense to continue looking at other rules once a deleted one is
> > rejected. Although the original example is fine, this makes it more
> > meaningful.
>
> Sorry, I messed up the patch title, it is supposed to be 'doc: rcu:
> ...'. I can resend it if you want.
Hmmm... There doesn't seem to be any consistent standard for documentation
patches. I see "Documentation: networking:", "docs:", "doc:" (which is
what I normally use), "doc:doc-guide:", "Documentation/process:",
"doc/devicetree:", "media: doc:", and who knows what all else.
Including "Documentation" seems excessive. I guess I am OK with
"doc: rcu:", but either just plain "doc:" or "doc/rcu:" would be fine
with me as well.
Thanx, Paul
next prev parent reply other threads:[~2018-10-28 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 2:16 [RFC] rcu: doc: update example about stale data Joel Fernandes (Google)
2018-10-28 4:44 ` Joel Fernandes
2018-10-28 17:29 ` Paul E. McKenney [this message]
2018-10-28 17:21 ` Paul E. McKenney
2018-10-29 1:16 ` Joel Fernandes
2018-10-30 23:50 ` Paul E. McKenney
2018-10-31 0:58 ` Joel Fernandes
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=20181028172918.GO4170@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.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 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.