From: "Paul E. McKenney" <paulmck@kernel.org>
To: Phong Tran <tranmanphong@gmail.com>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org,
jiangshanlai@gmail.com, josh@joshtriplett.org,
rostedt@goodmis.org, linux-kernel@vger.kernel.org,
rcu@vger.kernel.org, mathieu.desnoyers@efficios.com,
joel@joelfernandes.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] [PATCH] Doc: convert whatisRCU.txt to rst
Date: Fri, 1 Nov 2019 00:53:09 -0700 [thread overview]
Message-ID: <20191101075309.GH20975@paulmck-ThinkPad-P72> (raw)
Message-ID: <20191101075309.da_jHsFru7nA4d23NXNf4zQWA-158a-1YDsjVMXZoHE@z> (raw)
In-Reply-To: <35bb2f18-791a-caf3-957d-01e43a4b3afc@gmail.com>
On Fri, Nov 01, 2019 at 08:17:36AM +0700, Phong Tran wrote:
> Hi Paul,
> On 11/1/19 5:54 AM, Paul E. McKenney wrote:
> > Could you and Madhuparna please review and test each other's
> > .rst-conversion patches?
>
> It's fine.
> pull and "make SPHINXDIRS="RCU" htmldocs pdfdocs" rcu dev branch
> without error or warning.
Very good, thank you!
Once you have done that (or if you have already done that) and have
verified that the resulting .html and .pdf files for the changed portions
look good, you can respond with a Tested-by tag, which has "Tested-by:",
your name, and your email within "<" and ">". For example, commit
127068abe85b ("i2c: qcom-geni: Disable DMA processing on the Lenovo Yoga
C630") has this:
Tested-by: Bjorn Andersson <bjorn.andersson@linaro.org>
After you review the code, for example, by checking either the patch or the
resulting .rst file, you can respond with a very similar Reviewed-by tag.
Which allows you to get a start on participating in the code-review
process.
Thanx, Paul
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2019-11-01 7:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 23:31 [Linux-kernel-mentees] [PATCH] Doc: convert whatisRCU.txt to rst tranmanphong
2019-10-30 23:31 ` Phong Tran
2019-10-31 22:54 ` paulmck
2019-10-31 22:54 ` Paul E. McKenney
2019-10-31 22:54 ` Paul E. McKenney
2019-11-01 1:17 ` tranmanphong
2019-11-01 1:17 ` Phong Tran
2019-11-01 1:17 ` Phong Tran
2019-11-01 7:53 ` paulmck [this message]
2019-11-01 7:53 ` Paul E. McKenney
2019-11-01 7:53 ` Paul E. McKenney
2019-11-01 3:33 ` madhuparnabhowmik04
2019-11-01 3:33 ` Madhuparna Bhowmik
2019-11-01 3:33 ` Madhuparna Bhowmik
2019-11-01 7:53 ` paulmck
2019-11-01 7:53 ` Paul E. McKenney
2019-11-01 7:53 ` Paul E. McKenney
2019-11-02 8:31 ` madhuparnabhowmik04
2019-11-02 8:31 ` Madhuparna Bhowmik
2019-11-02 8:31 ` Madhuparna Bhowmik
2019-11-02 12:00 ` tranmanphong
2019-11-02 12:00 ` Phong Tran
2019-11-02 12:00 ` Phong Tran
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=20191101075309.GH20975@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=corbet@lwn.net \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tranmanphong@gmail.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 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).