From: joel at joelfernandes.org (Joel Fernandes)
Subject: [Linux-kernel-mentees] [PATCH v2 1/7] Documentation: RCU: Convert RCU basic concepts to ReST
Date: Sun, 23 Jun 2019 19:34:22 -0400 [thread overview]
Message-ID: <20190623233422.GC141282@google.com> (raw)
In-Reply-To: <20190623081413.7095-2-c0d1n61at3@gmail.com>
On Sun, Jun 23, 2019 at 03:14:07AM -0500, Jiunn Chang wrote:
> ReST markup and TOC tree hook.
>
> Signed-off-by: Jiunn Chang <c0d1n61at3 at gmail.com>
This one LGTM.
Reviewed-by: Joel Fernandes (Google) <joel at joelfernandes.org>
thanks,
- Joel
> ---
> Documentation/RCU/index.rst | 17 ++++++
> Documentation/RCU/rcu.txt | 114 ++++++++++++++++++------------------
> 2 files changed, 75 insertions(+), 56 deletions(-)
> create mode 100644 Documentation/RCU/index.rst
>
> diff --git a/Documentation/RCU/index.rst b/Documentation/RCU/index.rst
> new file mode 100644
> index 000000000000..bc8cd42a91cc
> --- /dev/null
> +++ b/Documentation/RCU/index.rst
> @@ -0,0 +1,17 @@
> +.. _rcu_concepts:
> +
> +============
> +RCU concepts
> +============
> +
> +.. toctree::
> + :maxdepth: 1
> +
> + rcu
> +
> +.. only:: subproject and html
> +
> + Indices
> + =======
> +
> + * :ref:`genindex`
> diff --git a/Documentation/RCU/rcu.txt b/Documentation/RCU/rcu.txt
> index c818cf65c5a9..2b93b128a6fd 100644
> --- a/Documentation/RCU/rcu.txt
> +++ b/Documentation/RCU/rcu.txt
> @@ -1,5 +1,8 @@
> -RCU Concepts
> +.. _rcu_doc:
>
> +============
> +RCU Concepts
> +============
>
> The basic idea behind RCU (read-copy update) is to split destructive
> operations into two parts, one that prevents anyone from seeing the data
> @@ -11,79 +14,78 @@ from a linked list would first remove the item from the list, wait for
> a grace period to elapse, then free the element. See the listRCU.txt
> file for more information on using RCU with linked lists.
>
> -
> Frequently Asked Questions
>
> -o Why would anyone want to use RCU?
> +- Why would anyone want to use RCU?
>
> - The advantage of RCU's two-part approach is that RCU readers need
> - not acquire any locks, perform any atomic instructions, write to
> - shared memory, or (on CPUs other than Alpha) execute any memory
> - barriers. The fact that these operations are quite expensive
> - on modern CPUs is what gives RCU its performance advantages
> - in read-mostly situations. The fact that RCU readers need not
> - acquire locks can also greatly simplify deadlock-avoidance code.
> + The advantage of RCU's two-part approach is that RCU readers need
> + not acquire any locks, perform any atomic instructions, write to
> + shared memory, or (on CPUs other than Alpha) execute any memory
> + barriers. The fact that these operations are quite expensive
> + on modern CPUs is what gives RCU its performance advantages
> + in read-mostly situations. The fact that RCU readers need not
> + acquire locks can also greatly simplify deadlock-avoidance code.
>
> -o How can the updater tell when a grace period has completed
> - if the RCU readers give no indication when they are done?
> +- How can the updater tell when a grace period has completed
> + if the RCU readers give no indication when they are done?
>
> - Just as with spinlocks, RCU readers are not permitted to
> - block, switch to user-mode execution, or enter the idle loop.
> - Therefore, as soon as a CPU is seen passing through any of these
> - three states, we know that that CPU has exited any previous RCU
> - read-side critical sections. So, if we remove an item from a
> - linked list, and then wait until all CPUs have switched context,
> - executed in user mode, or executed in the idle loop, we can
> - safely free up that item.
> + Just as with spinlocks, RCU readers are not permitted to
> + block, switch to user-mode execution, or enter the idle loop.
> + Therefore, as soon as a CPU is seen passing through any of these
> + three states, we know that that CPU has exited any previous RCU
> + read-side critical sections. So, if we remove an item from a
> + linked list, and then wait until all CPUs have switched context,
> + executed in user mode, or executed in the idle loop, we can
> + safely free up that item.
>
> - Preemptible variants of RCU (CONFIG_PREEMPT_RCU) get the
> - same effect, but require that the readers manipulate CPU-local
> - counters. These counters allow limited types of blocking within
> - RCU read-side critical sections. SRCU also uses CPU-local
> - counters, and permits general blocking within RCU read-side
> - critical sections. These variants of RCU detect grace periods
> - by sampling these counters.
> + Preemptible variants of RCU (CONFIG_PREEMPT_RCU) get the
> + same effect, but require that the readers manipulate CPU-local
> + counters. These counters allow limited types of blocking within
> + RCU read-side critical sections. SRCU also uses CPU-local
> + counters, and permits general blocking within RCU read-side
> + critical sections. These variants of RCU detect grace periods
> + by sampling these counters.
>
> -o If I am running on a uniprocessor kernel, which can only do one
> - thing at a time, why should I wait for a grace period?
> +- If I am running on a uniprocessor kernel, which can only do one
> + thing at a time, why should I wait for a grace period?
>
> - See the UP.txt file in this directory.
> + See the UP.txt file in this directory.
>
> -o How can I see where RCU is currently used in the Linux kernel?
> +- How can I see where RCU is currently used in the Linux kernel?
>
> - Search for "rcu_read_lock", "rcu_read_unlock", "call_rcu",
> - "rcu_read_lock_bh", "rcu_read_unlock_bh", "srcu_read_lock",
> - "srcu_read_unlock", "synchronize_rcu", "synchronize_net",
> - "synchronize_srcu", and the other RCU primitives. Or grab one
> - of the cscope databases from:
> + Search for "rcu_read_lock", "rcu_read_unlock", "call_rcu",
> + "rcu_read_lock_bh", "rcu_read_unlock_bh", "srcu_read_lock",
> + "srcu_read_unlock", "synchronize_rcu", "synchronize_net",
> + "synchronize_srcu", and the other RCU primitives. Or grab one
> + of the cscope databases from:
>
> - http://www.rdrop.com/users/paulmck/RCU/linuxusage/rculocktab.html
> + (http://www.rdrop.com/users/paulmck/RCU/linuxusage/rculocktab.html).
>
> -o What guidelines should I follow when writing code that uses RCU?
> +- What guidelines should I follow when writing code that uses RCU?
>
> - See the checklist.txt file in this directory.
> + See the checklist.txt file in this directory.
>
> -o Why the name "RCU"?
> +- Why the name "RCU"?
>
> - "RCU" stands for "read-copy update". The file listRCU.txt has
> - more information on where this name came from, search for
> - "read-copy update" to find it.
> + "RCU" stands for "read-copy update". The file listRCU.txt has
> + more information on where this name came from, search for
> + "read-copy update" to find it.
>
> -o I hear that RCU is patented? What is with that?
> +- I hear that RCU is patented? What is with that?
>
> - Yes, it is. There are several known patents related to RCU,
> - search for the string "Patent" in RTFP.txt to find them.
> - Of these, one was allowed to lapse by the assignee, and the
> - others have been contributed to the Linux kernel under GPL.
> - There are now also LGPL implementations of user-level RCU
> - available (http://liburcu.org/).
> + Yes, it is. There are several known patents related to RCU,
> + search for the string "Patent" in RTFP.txt to find them.
> + Of these, one was allowed to lapse by the assignee, and the
> + others have been contributed to the Linux kernel under GPL.
> + There are now also LGPL implementations of user-level RCU
> + available (http://liburcu.org/).
>
> -o I hear that RCU needs work in order to support realtime kernels?
> +- I hear that RCU needs work in order to support realtime kernels?
>
> - Realtime-friendly RCU can be enabled via the CONFIG_PREEMPT_RCU
> - kernel configuration parameter.
> + Realtime-friendly RCU can be enabled via the CONFIG_PREEMPT_RCU
> + kernel configuration parameter.
>
> -o Where can I find more information on RCU?
> +- Where can I find more information on RCU?
>
> - See the RTFP.txt file in this directory.
> - Or point your browser at http://www.rdrop.com/users/paulmck/RCU/.
> + See the RTFP.txt file in this directory.
> + Or point your browser at (http://www.rdrop.com/users/paulmck/RCU/).
> --
> 2.22.0
>
WARNING: multiple messages have this Message-ID (diff)
From: joel@joelfernandes.org (Joel Fernandes)
Subject: [Linux-kernel-mentees] [PATCH v2 1/7] Documentation: RCU: Convert RCU basic concepts to ReST
Date: Sun, 23 Jun 2019 19:34:22 -0400 [thread overview]
Message-ID: <20190623233422.GC141282@google.com> (raw)
Message-ID: <20190623233422.wpJxYBCRbWQMVBYu2kD5pjiaQo1WddB1pTgYyhYHoAU@z> (raw)
In-Reply-To: <20190623081413.7095-2-c0d1n61at3@gmail.com>
On Sun, Jun 23, 2019 at 03:14:07AM -0500, Jiunn Chang wrote:
> ReST markup and TOC tree hook.
>
> Signed-off-by: Jiunn Chang <c0d1n61at3 at gmail.com>
This one LGTM.
Reviewed-by: Joel Fernandes (Google) <joel at joelfernandes.org>
thanks,
- Joel
> ---
> Documentation/RCU/index.rst | 17 ++++++
> Documentation/RCU/rcu.txt | 114 ++++++++++++++++++------------------
> 2 files changed, 75 insertions(+), 56 deletions(-)
> create mode 100644 Documentation/RCU/index.rst
>
> diff --git a/Documentation/RCU/index.rst b/Documentation/RCU/index.rst
> new file mode 100644
> index 000000000000..bc8cd42a91cc
> --- /dev/null
> +++ b/Documentation/RCU/index.rst
> @@ -0,0 +1,17 @@
> +.. _rcu_concepts:
> +
> +============
> +RCU concepts
> +============
> +
> +.. toctree::
> + :maxdepth: 1
> +
> + rcu
> +
> +.. only:: subproject and html
> +
> + Indices
> + =======
> +
> + * :ref:`genindex`
> diff --git a/Documentation/RCU/rcu.txt b/Documentation/RCU/rcu.txt
> index c818cf65c5a9..2b93b128a6fd 100644
> --- a/Documentation/RCU/rcu.txt
> +++ b/Documentation/RCU/rcu.txt
> @@ -1,5 +1,8 @@
> -RCU Concepts
> +.. _rcu_doc:
>
> +============
> +RCU Concepts
> +============
>
> The basic idea behind RCU (read-copy update) is to split destructive
> operations into two parts, one that prevents anyone from seeing the data
> @@ -11,79 +14,78 @@ from a linked list would first remove the item from the list, wait for
> a grace period to elapse, then free the element. See the listRCU.txt
> file for more information on using RCU with linked lists.
>
> -
> Frequently Asked Questions
>
> -o Why would anyone want to use RCU?
> +- Why would anyone want to use RCU?
>
> - The advantage of RCU's two-part approach is that RCU readers need
> - not acquire any locks, perform any atomic instructions, write to
> - shared memory, or (on CPUs other than Alpha) execute any memory
> - barriers. The fact that these operations are quite expensive
> - on modern CPUs is what gives RCU its performance advantages
> - in read-mostly situations. The fact that RCU readers need not
> - acquire locks can also greatly simplify deadlock-avoidance code.
> + The advantage of RCU's two-part approach is that RCU readers need
> + not acquire any locks, perform any atomic instructions, write to
> + shared memory, or (on CPUs other than Alpha) execute any memory
> + barriers. The fact that these operations are quite expensive
> + on modern CPUs is what gives RCU its performance advantages
> + in read-mostly situations. The fact that RCU readers need not
> + acquire locks can also greatly simplify deadlock-avoidance code.
>
> -o How can the updater tell when a grace period has completed
> - if the RCU readers give no indication when they are done?
> +- How can the updater tell when a grace period has completed
> + if the RCU readers give no indication when they are done?
>
> - Just as with spinlocks, RCU readers are not permitted to
> - block, switch to user-mode execution, or enter the idle loop.
> - Therefore, as soon as a CPU is seen passing through any of these
> - three states, we know that that CPU has exited any previous RCU
> - read-side critical sections. So, if we remove an item from a
> - linked list, and then wait until all CPUs have switched context,
> - executed in user mode, or executed in the idle loop, we can
> - safely free up that item.
> + Just as with spinlocks, RCU readers are not permitted to
> + block, switch to user-mode execution, or enter the idle loop.
> + Therefore, as soon as a CPU is seen passing through any of these
> + three states, we know that that CPU has exited any previous RCU
> + read-side critical sections. So, if we remove an item from a
> + linked list, and then wait until all CPUs have switched context,
> + executed in user mode, or executed in the idle loop, we can
> + safely free up that item.
>
> - Preemptible variants of RCU (CONFIG_PREEMPT_RCU) get the
> - same effect, but require that the readers manipulate CPU-local
> - counters. These counters allow limited types of blocking within
> - RCU read-side critical sections. SRCU also uses CPU-local
> - counters, and permits general blocking within RCU read-side
> - critical sections. These variants of RCU detect grace periods
> - by sampling these counters.
> + Preemptible variants of RCU (CONFIG_PREEMPT_RCU) get the
> + same effect, but require that the readers manipulate CPU-local
> + counters. These counters allow limited types of blocking within
> + RCU read-side critical sections. SRCU also uses CPU-local
> + counters, and permits general blocking within RCU read-side
> + critical sections. These variants of RCU detect grace periods
> + by sampling these counters.
>
> -o If I am running on a uniprocessor kernel, which can only do one
> - thing at a time, why should I wait for a grace period?
> +- If I am running on a uniprocessor kernel, which can only do one
> + thing at a time, why should I wait for a grace period?
>
> - See the UP.txt file in this directory.
> + See the UP.txt file in this directory.
>
> -o How can I see where RCU is currently used in the Linux kernel?
> +- How can I see where RCU is currently used in the Linux kernel?
>
> - Search for "rcu_read_lock", "rcu_read_unlock", "call_rcu",
> - "rcu_read_lock_bh", "rcu_read_unlock_bh", "srcu_read_lock",
> - "srcu_read_unlock", "synchronize_rcu", "synchronize_net",
> - "synchronize_srcu", and the other RCU primitives. Or grab one
> - of the cscope databases from:
> + Search for "rcu_read_lock", "rcu_read_unlock", "call_rcu",
> + "rcu_read_lock_bh", "rcu_read_unlock_bh", "srcu_read_lock",
> + "srcu_read_unlock", "synchronize_rcu", "synchronize_net",
> + "synchronize_srcu", and the other RCU primitives. Or grab one
> + of the cscope databases from:
>
> - http://www.rdrop.com/users/paulmck/RCU/linuxusage/rculocktab.html
> + (http://www.rdrop.com/users/paulmck/RCU/linuxusage/rculocktab.html).
>
> -o What guidelines should I follow when writing code that uses RCU?
> +- What guidelines should I follow when writing code that uses RCU?
>
> - See the checklist.txt file in this directory.
> + See the checklist.txt file in this directory.
>
> -o Why the name "RCU"?
> +- Why the name "RCU"?
>
> - "RCU" stands for "read-copy update". The file listRCU.txt has
> - more information on where this name came from, search for
> - "read-copy update" to find it.
> + "RCU" stands for "read-copy update". The file listRCU.txt has
> + more information on where this name came from, search for
> + "read-copy update" to find it.
>
> -o I hear that RCU is patented? What is with that?
> +- I hear that RCU is patented? What is with that?
>
> - Yes, it is. There are several known patents related to RCU,
> - search for the string "Patent" in RTFP.txt to find them.
> - Of these, one was allowed to lapse by the assignee, and the
> - others have been contributed to the Linux kernel under GPL.
> - There are now also LGPL implementations of user-level RCU
> - available (http://liburcu.org/).
> + Yes, it is. There are several known patents related to RCU,
> + search for the string "Patent" in RTFP.txt to find them.
> + Of these, one was allowed to lapse by the assignee, and the
> + others have been contributed to the Linux kernel under GPL.
> + There are now also LGPL implementations of user-level RCU
> + available (http://liburcu.org/).
>
> -o I hear that RCU needs work in order to support realtime kernels?
> +- I hear that RCU needs work in order to support realtime kernels?
>
> - Realtime-friendly RCU can be enabled via the CONFIG_PREEMPT_RCU
> - kernel configuration parameter.
> + Realtime-friendly RCU can be enabled via the CONFIG_PREEMPT_RCU
> + kernel configuration parameter.
>
> -o Where can I find more information on RCU?
> +- Where can I find more information on RCU?
>
> - See the RTFP.txt file in this directory.
> - Or point your browser at http://www.rdrop.com/users/paulmck/RCU/.
> + See the RTFP.txt file in this directory.
> + Or point your browser at (http://www.rdrop.com/users/paulmck/RCU/).
> --
> 2.22.0
>
next prev parent reply other threads:[~2019-06-23 23:34 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 7:02 [Linux-kernel-mentees] [PATCH 2/3] Documentation: RCU: Convert RCU linked list to ReST c0d1n61at3
2019-06-22 7:02 ` Jiunn Chang
2019-06-22 15:00 ` corbet
2019-06-22 15:00 ` Jonathan Corbet
2019-06-23 8:14 ` [Linux-kernel-mentees] [PATCH v2 0/7] Documentation: RCU: Convert to c0d1n61at3
2019-06-23 8:14 ` Jiunn Chang
2019-06-23 23:39 ` joel
2019-06-23 23:39 ` Joel Fernandes
2019-06-24 0:39 ` corbet
2019-06-24 0:39 ` Jonathan Corbet
2019-06-25 6:26 ` [Linux-kernel-mentees] [PATCH v3 0/6] Documentation: RCU: Convert to reST c0d1n61at3
2019-06-25 6:26 ` Jiunn Chang
2019-06-26 19:12 ` [Linux-kernel-mentees] [PATCH v4 0/5] " c0d1n61at3
2019-06-26 19:12 ` Jiunn Chang
2019-06-26 20:07 ` [Linux-kernel-mentees] [PATCH v5 " c0d1n61at3
2019-06-26 20:07 ` Jiunn Chang
2019-06-26 20:07 ` [Linux-kernel-mentees] [PATCH v5 1/5] Documentation: RCU: Convert RCU basic concepts " c0d1n61at3
2019-06-26 20:07 ` Jiunn Chang
2019-06-27 14:34 ` corbet
2019-06-27 14:34 ` Jonathan Corbet
2019-06-27 15:13 ` rostedt
2019-06-27 15:13 ` Steven Rostedt
2019-06-27 16:48 ` skhan
2019-06-27 16:48 ` Shuah Khan
2019-06-27 16:26 ` paulmck
2019-06-27 16:26 ` Paul E. McKenney
2019-06-27 16:47 ` c0d1n61at3
2019-06-27 16:47 ` Jiunn Chang
2019-06-26 20:07 ` [Linux-kernel-mentees] [PATCH v5 2/5] Documentation: RCU: Convert RCU linked list " c0d1n61at3
2019-06-26 20:07 ` Jiunn Chang
2019-06-26 20:07 ` [Linux-kernel-mentees] [PATCH v5 3/5] Documentation: RCU: Convert RCU UP systems " c0d1n61at3
2019-06-26 20:07 ` Jiunn Chang
2019-06-26 20:07 ` [Linux-kernel-mentees] [PATCH v5 4/5] Documentation: RCU: Rename txt files to rst c0d1n61at3
2019-06-26 20:07 ` Jiunn Chang
2019-06-26 20:07 ` [Linux-kernel-mentees] [PATCH v5 5/5] Documentation: RCU: Add TOC tree hooks c0d1n61at3
2019-06-26 20:07 ` Jiunn Chang
2019-06-26 19:12 ` [Linux-kernel-mentees] [PATCH v4 1/5] Documentation: RCU: Convert RCU basic concepts to reST c0d1n61at3
2019-06-26 19:12 ` Jiunn Chang
2019-06-26 19:12 ` [Linux-kernel-mentees] [PATCH v4 2/5] Documentation: RCU: Convert RCU linked list " c0d1n61at3
2019-06-26 19:12 ` Jiunn Chang
2019-06-26 19:12 ` [Linux-kernel-mentees] [PATCH v4 3/5] Documentation: RCU: Convert RCU UP systems " c0d1n61at3
2019-06-26 19:12 ` Jiunn Chang
2019-06-26 19:12 ` [Linux-kernel-mentees] [PATCH v4 4/5] Documentation: RCU: Rename txt files to rst c0d1n61at3
2019-06-26 19:12 ` Jiunn Chang
2019-06-26 19:12 ` [Linux-kernel-mentees] [PATCH v4 5/5] Documentation: RCU: Add TOC tree hooks c0d1n61at3
2019-06-26 19:12 ` Jiunn Chang
2019-06-25 6:26 ` [Linux-kernel-mentees] [PATCH v3 1/6] Documentation: RCU: Convert RCU basic concepts to reST c0d1n61at3
2019-06-25 6:26 ` Jiunn Chang
2019-06-25 6:26 ` [Linux-kernel-mentees] [PATCH v3 2/6] Documentation: RCU: Convert RCU linked list " c0d1n61at3
2019-06-25 6:26 ` Jiunn Chang
2019-06-25 6:26 ` [Linux-kernel-mentees] [PATCH v3 3/6] Documentation: RCU: Convert RCU UP systems " c0d1n61at3
2019-06-25 6:26 ` Jiunn Chang
2019-06-25 16:03 ` paulmck
2019-06-25 16:03 ` Paul E. McKenney
2019-06-25 6:26 ` [Linux-kernel-mentees] [PATCH v3 4/6] Documentation: RCU: Rename txt files to rst c0d1n61at3
2019-06-25 6:26 ` Jiunn Chang
2019-06-25 6:26 ` [Linux-kernel-mentees] [PATCH v3 5/6] Documentation: RCU: Add links to rcu.rst c0d1n61at3
2019-06-25 6:26 ` Jiunn Chang
2019-06-25 15:56 ` paulmck
2019-06-25 15:56 ` Paul E. McKenney
2019-06-25 21:01 ` corbet
2019-06-25 21:01 ` Jonathan Corbet
2019-06-25 21:17 ` paulmck
2019-06-25 21:17 ` Paul E. McKenney
2019-06-25 21:40 ` corbet
2019-06-25 21:40 ` Jonathan Corbet
2019-06-25 21:45 ` paulmck
2019-06-25 21:45 ` Paul E. McKenney
2019-06-25 6:26 ` [Linux-kernel-mentees] [PATCH v3 6/6] Documentation: RCU: Add TOC tree hooks c0d1n61at3
2019-06-25 6:26 ` Jiunn Chang
2019-06-23 8:14 ` [Linux-kernel-mentees] [PATCH v2 1/7] Documentation: RCU: Convert RCU basic concepts to ReST c0d1n61at3
2019-06-23 8:14 ` Jiunn Chang
2019-06-23 23:34 ` joel [this message]
2019-06-23 23:34 ` Joel Fernandes
2019-06-23 8:14 ` [Linux-kernel-mentees] [PATCH v2 2/7] Documentation: RCU: Rename " c0d1n61at3
2019-06-23 8:14 ` Jiunn Chang
2019-06-23 8:14 ` [Linux-kernel-mentees] [PATCH v2 3/7] Documentation: RCU: Convert RCU linked list " c0d1n61at3
2019-06-23 8:14 ` Jiunn Chang
2019-06-23 23:31 ` joel
2019-06-23 23:31 ` Joel Fernandes
2019-06-24 0:43 ` corbet
2019-06-24 0:43 ` Jonathan Corbet
2019-06-23 8:14 ` [Linux-kernel-mentees] [PATCH v2 4/7] Documentation: RCU: Rename " c0d1n61at3
2019-06-23 8:14 ` Jiunn Chang
2019-06-23 8:14 ` [Linux-kernel-mentees] [PATCH v2 5/7] Documentation: RCU: Convert RCU UP systems " c0d1n61at3
2019-06-23 8:14 ` Jiunn Chang
2019-06-23 23:27 ` joel
2019-06-23 23:27 ` Joel Fernandes
2019-06-24 0:45 ` corbet
2019-06-24 0:45 ` Jonathan Corbet
2019-06-23 8:14 ` [Linux-kernel-mentees] [PATCH v2 6/7] Documentation: RCU: Rename " c0d1n61at3
2019-06-23 8:14 ` Jiunn Chang
2019-06-23 8:14 ` [Linux-kernel-mentees] [PATCH v2 7/7] Documentation: RCU: Add links to rcu.rst c0d1n61at3
2019-06-23 8:14 ` Jiunn Chang
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=20190623233422.GC141282@google.com \
--to=linux-kernel-mentees@lists.linux-foundation.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