From: paulmck at linux.ibm.com (Paul E. McKenney)
Subject: [Linux-kernel-mentees] [PATCH 1/3] Documentation: RCU: Convert RCU basic concepts to ReST
Date: Sat, 22 Jun 2019 10:03:31 -0700 [thread overview]
Message-ID: <20190622170331.GR26519@linux.ibm.com> (raw)
In-Reply-To: <20190622085411.3c1692c2@lwn.net>
On Sat, Jun 22, 2019 at 08:54:11AM -0600, Jonathan Corbet wrote:
> On Sat, 22 Jun 2019 02:01:33 -0500
> Jiunn Chang <c0d1n61at3 at gmail.com> wrote:
>
> > Convert RCU basic concepts and add TOC tree hook.
> >
> > Signed-off-by: Jiunn Chang <c0d1n61at3 at gmail.com>
>
> A few overall comments...
>
> - Hopefully Paul is OK with converting these documents. If not, Paul,
> now seems like the time to complain :)
No complaints here!
> - It's good to have a cover letter on a multi-part patch set like this
> describing the overall project. It's also important to copy patches to
> a public list. At a minimum, linux-doc would be a good place; I'd
> suggest linux-kernel as well - it doesn't get enough email and people
> get lonely there.
Heh! For RCU documentation patches, please also CC rcu at vger.kernel.org.
> - (The part that people get mad at me about): we should think about
> whether this should remain a top-level directory. I would argue for
> putting it into the core-api manual, but others may disagree.
Let's worry about that separately.
> Thanks for working to improve our docs! In this case, the conversion
> itself looks good.
I will do a build and check within the next few days, and will more
carefully review your next version of this patch series.
Thanx, Paul
WARNING: multiple messages have this Message-ID (diff)
From: paulmck@linux.ibm.com (Paul E. McKenney)
Subject: [Linux-kernel-mentees] [PATCH 1/3] Documentation: RCU: Convert RCU basic concepts to ReST
Date: Sat, 22 Jun 2019 10:03:31 -0700 [thread overview]
Message-ID: <20190622170331.GR26519@linux.ibm.com> (raw)
Message-ID: <20190622170331.5Z18q1r2f2p7kb1DN-D0GlrEC58l2IzOygr9IAsA1hw@z> (raw)
In-Reply-To: <20190622085411.3c1692c2@lwn.net>
On Sat, Jun 22, 2019 at 08:54:11AM -0600, Jonathan Corbet wrote:
> On Sat, 22 Jun 2019 02:01:33 -0500
> Jiunn Chang <c0d1n61at3 at gmail.com> wrote:
>
> > Convert RCU basic concepts and add TOC tree hook.
> >
> > Signed-off-by: Jiunn Chang <c0d1n61at3 at gmail.com>
>
> A few overall comments...
>
> - Hopefully Paul is OK with converting these documents. If not, Paul,
> now seems like the time to complain :)
No complaints here!
> - It's good to have a cover letter on a multi-part patch set like this
> describing the overall project. It's also important to copy patches to
> a public list. At a minimum, linux-doc would be a good place; I'd
> suggest linux-kernel as well - it doesn't get enough email and people
> get lonely there.
Heh! For RCU documentation patches, please also CC rcu at vger.kernel.org.
> - (The part that people get mad at me about): we should think about
> whether this should remain a top-level directory. I would argue for
> putting it into the core-api manual, but others may disagree.
Let's worry about that separately.
> Thanks for working to improve our docs! In this case, the conversion
> itself looks good.
I will do a build and check within the next few days, and will more
carefully review your next version of this patch series.
Thanx, Paul
next prev parent reply other threads:[~2019-06-22 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 7:01 [Linux-kernel-mentees] [PATCH 1/3] Documentation: RCU: Convert RCU basic concepts to ReST c0d1n61at3
2019-06-22 7:01 ` Jiunn Chang
2019-06-22 14:54 ` corbet
2019-06-22 14:54 ` Jonathan Corbet
2019-06-22 17:03 ` paulmck [this message]
2019-06-22 17:03 ` Paul E. McKenney
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=20190622170331.GR26519@linux.ibm.com \
--to=unknown@example.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 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.