All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Shuah Khan <shuah@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 30/32] selftests/ftrace: Add ftrace cpumask testcase
Date: Fri, 24 Aug 2018 22:18:22 -0400	[thread overview]
Message-ID: <20180824221822.3e0092c9@vmware.local.home> (raw)
In-Reply-To: <153443780039.23257.5243924038958174104.stgit@devbox>

On Fri, 17 Aug 2018 01:43:20 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:

> Add a testcase for tracing_cpumask with function tracer.
> 
> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> ---
>  .../selftests/ftrace/test.d/ftrace/func_cpumask.tc |   34 ++++++++++++++++++++
>  1 file changed, 34 insertions(+)
>  create mode 100644 tools/testing/selftests/ftrace/test.d/ftrace/func_cpumask.tc
> 
> diff --git a/tools/testing/selftests/ftrace/test.d/ftrace/func_cpumask.tc b/tools/testing/selftests/ftrace/test.d/ftrace/func_cpumask.tc
> new file mode 100644
> index 000000000000..37420e355445
> --- /dev/null
> +++ b/tools/testing/selftests/ftrace/test.d/ftrace/func_cpumask.tc
> @@ -0,0 +1,34 @@
> +#!/bin/sh
> +# SPDX-License-Identifier: GPL2.0
> +# description: ftrace - function trace with cpumask
> +
> +NP=`grep "^processor" /proc/cpuinfo | wc -l`

A better way to find the number of CPUs is to either use "nproc" or
just look at /sys/devices/system/cpu/cpu[0-9]*. Because what I learned
from experience is that searching for strings in /proc/cpuinfo is not
cross arch compatible. For example, other archs don't use "processor"
in the stings and would come up with a box with 0 CPUs. Something we've
been working on for some time ;-)

-- Steve

> +
> +if [ $NP -eq 1 ] ;then
> +  echo "We can not test cpumask on UP environment"
> +  exit_unresolved
> +fi
> +
> +do_reset() {
> +  echo ffff > tracing_cpumask

Why ffff? Should we save what was in tracing_cpumask first and just
reuse it?

-- Steve


> +}
> +
> +echo 0 > tracing_on
> +echo > trace
> +: "Bitmask only record on CPU1"
> +echo 2 > tracing_cpumask
> +MASK=0x`cat tracing_cpumask`
> +test `printf "%d" $MASK` -eq 2 || do_reset
> +
> +echo function > current_tracer
> +echo 1 > tracing_on
> +(echo "forked")
> +echo 0 > tracing_on
> +
> +: "Check CPU1 events are recorded"
> +grep -q -e "\[001\]" trace || do_reset
> +
> +: "There should be No other cpu events"
> +! grep -qv -e "\[001\]" -e "^#" trace || do_reset
> +
> +do_reset


WARNING: multiple messages have this Message-ID (diff)
From: rostedt at goodmis.org (Steven Rostedt)
Subject: [PATCH v2 30/32] selftests/ftrace: Add ftrace cpumask testcase
Date: Fri, 24 Aug 2018 22:18:22 -0400	[thread overview]
Message-ID: <20180824221822.3e0092c9@vmware.local.home> (raw)
In-Reply-To: <153443780039.23257.5243924038958174104.stgit@devbox>

On Fri, 17 Aug 2018 01:43:20 +0900
Masami Hiramatsu <mhiramat at kernel.org> wrote:

> Add a testcase for tracing_cpumask with function tracer.
> 
> Signed-off-by: Masami Hiramatsu <mhiramat at kernel.org>
> ---
>  .../selftests/ftrace/test.d/ftrace/func_cpumask.tc |   34 ++++++++++++++++++++
>  1 file changed, 34 insertions(+)
>  create mode 100644 tools/testing/selftests/ftrace/test.d/ftrace/func_cpumask.tc
> 
> diff --git a/tools/testing/selftests/ftrace/test.d/ftrace/func_cpumask.tc b/tools/testing/selftests/ftrace/test.d/ftrace/func_cpumask.tc
> new file mode 100644
> index 000000000000..37420e355445
> --- /dev/null
> +++ b/tools/testing/selftests/ftrace/test.d/ftrace/func_cpumask.tc
> @@ -0,0 +1,34 @@
> +#!/bin/sh
> +# SPDX-License-Identifier: GPL2.0
> +# description: ftrace - function trace with cpumask
> +
> +NP=`grep "^processor" /proc/cpuinfo | wc -l`

A better way to find the number of CPUs is to either use "nproc" or
just look at /sys/devices/system/cpu/cpu[0-9]*. Because what I learned
from experience is that searching for strings in /proc/cpuinfo is not
cross arch compatible. For example, other archs don't use "processor"
in the stings and would come up with a box with 0 CPUs. Something we've
been working on for some time ;-)

-- Steve

> +
> +if [ $NP -eq 1 ] ;then
> +  echo "We can not test cpumask on UP environment"
> +  exit_unresolved
> +fi
> +
> +do_reset() {
> +  echo ffff > tracing_cpumask

Why ffff? Should we save what was in tracing_cpumask first and just
reuse it?

-- Steve


> +}
> +
> +echo 0 > tracing_on
> +echo > trace
> +: "Bitmask only record on CPU1"
> +echo 2 > tracing_cpumask
> +MASK=0x`cat tracing_cpumask`
> +test `printf "%d" $MASK` -eq 2 || do_reset
> +
> +echo function > current_tracer
> +echo 1 > tracing_on
> +(echo "forked")
> +echo 0 > tracing_on
> +
> +: "Check CPU1 events are recorded"
> +grep -q -e "\[001\]" trace || do_reset
> +
> +: "There should be No other cpu events"
> +! grep -qv -e "\[001\]" -e "^#" trace || do_reset
> +
> +do_reset

WARNING: multiple messages have this Message-ID (diff)
From: rostedt@goodmis.org (Steven Rostedt)
Subject: [PATCH v2 30/32] selftests/ftrace: Add ftrace cpumask testcase
Date: Fri, 24 Aug 2018 22:18:22 -0400	[thread overview]
Message-ID: <20180824221822.3e0092c9@vmware.local.home> (raw)
Message-ID: <20180825021822.uX_ruY-5DMRSQZ8EbWQ8knPLjiRoG0cOqQhIpGIamOA@z> (raw)
In-Reply-To: <153443780039.23257.5243924038958174104.stgit@devbox>

On Fri, 17 Aug 2018 01:43:20 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:

> Add a testcase for tracing_cpumask with function tracer.
> 
> Signed-off-by: Masami Hiramatsu <mhiramat at kernel.org>
> ---
>  .../selftests/ftrace/test.d/ftrace/func_cpumask.tc |   34 ++++++++++++++++++++
>  1 file changed, 34 insertions(+)
>  create mode 100644 tools/testing/selftests/ftrace/test.d/ftrace/func_cpumask.tc
> 
> diff --git a/tools/testing/selftests/ftrace/test.d/ftrace/func_cpumask.tc b/tools/testing/selftests/ftrace/test.d/ftrace/func_cpumask.tc
> new file mode 100644
> index 000000000000..37420e355445
> --- /dev/null
> +++ b/tools/testing/selftests/ftrace/test.d/ftrace/func_cpumask.tc
> @@ -0,0 +1,34 @@
> +#!/bin/sh
> +# SPDX-License-Identifier: GPL2.0
> +# description: ftrace - function trace with cpumask
> +
> +NP=`grep "^processor" /proc/cpuinfo | wc -l`

A better way to find the number of CPUs is to either use "nproc" or
just look at /sys/devices/system/cpu/cpu[0-9]*. Because what I learned
from experience is that searching for strings in /proc/cpuinfo is not
cross arch compatible. For example, other archs don't use "processor"
in the stings and would come up with a box with 0 CPUs. Something we've
been working on for some time ;-)

-- Steve

> +
> +if [ $NP -eq 1 ] ;then
> +  echo "We can not test cpumask on UP environment"
> +  exit_unresolved
> +fi
> +
> +do_reset() {
> +  echo ffff > tracing_cpumask

Why ffff? Should we save what was in tracing_cpumask first and just
reuse it?

-- Steve


> +}
> +
> +echo 0 > tracing_on
> +echo > trace
> +: "Bitmask only record on CPU1"
> +echo 2 > tracing_cpumask
> +MASK=0x`cat tracing_cpumask`
> +test `printf "%d" $MASK` -eq 2 || do_reset
> +
> +echo function > current_tracer
> +echo 1 > tracing_on
> +(echo "forked")
> +echo 0 > tracing_on
> +
> +: "Check CPU1 events are recorded"
> +grep -q -e "\[001\]" trace || do_reset
> +
> +: "There should be No other cpu events"
> +! grep -qv -e "\[001\]" -e "^#" trace || do_reset
> +
> +do_reset

  reply	other threads:[~2018-08-25  2:18 UTC|newest]

Thread overview: 230+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16 16:29 [PATCH v2 00/32] selftests/ftrace: Improve ftracetest with coverage check Masami Hiramatsu
2018-08-16 16:29 ` Masami Hiramatsu
2018-08-16 16:29 ` mhiramat
2018-08-16 16:29 ` [PATCH v2 01/32] tracing: Allow gcov profiling on only ftrace subsystem Masami Hiramatsu
2018-08-16 16:29   ` Masami Hiramatsu
2018-08-16 16:29   ` mhiramat
2018-08-20 15:32   ` Steven Rostedt
2018-08-20 15:32     ` Steven Rostedt
2018-08-20 15:32     ` rostedt
2018-08-20 15:33     ` Steven Rostedt
2018-08-20 15:33       ` Steven Rostedt
2018-08-20 15:33       ` rostedt
2018-08-21  6:53       ` Masami Hiramatsu
2018-08-21  6:53         ` Masami Hiramatsu
2018-08-21  6:53         ` mhiramat
2018-08-21  7:27       ` [PATCH v2.1] " Masami Hiramatsu
2018-08-21 13:12         ` Steven Rostedt
2018-08-16 16:30 ` [PATCH v2 02/32] selftests/ftrace: Add --stop-fail hidden option for debug Masami Hiramatsu
2018-08-16 16:30   ` Masami Hiramatsu
2018-08-16 16:30   ` mhiramat
2018-08-24 20:38   ` Steven Rostedt
2018-08-24 20:38     ` Steven Rostedt
2018-08-24 20:38     ` rostedt
2018-08-16 16:30 ` [PATCH v2 03/32] selftests/ftrace: Add --console hidden option Masami Hiramatsu
2018-08-16 16:30   ` Masami Hiramatsu
2018-08-16 16:30   ` mhiramat
2018-08-24 20:37   ` Steven Rostedt
2018-08-24 20:37     ` Steven Rostedt
2018-08-24 20:37     ` rostedt
2018-08-25  1:35     ` Masami Hiramatsu
2018-08-25  1:35       ` Masami Hiramatsu
2018-08-25  1:35       ` mhiramat
2018-08-25  1:42       ` Steven Rostedt
2018-08-25  1:42         ` Steven Rostedt
2018-08-25  1:42         ` rostedt
2018-08-26  7:28         ` Masami Hiramatsu
2018-08-26  7:28           ` Masami Hiramatsu
2018-08-26  7:28           ` mhiramat
2018-08-16 16:31 ` [PATCH v2 04/32] selftests/ftrace: Add case number prefix to logfile Masami Hiramatsu
2018-08-16 16:31   ` Masami Hiramatsu
2018-08-16 16:31   ` mhiramat
2018-08-24 21:47   ` Steven Rostedt
2018-08-24 21:47     ` Steven Rostedt
2018-08-24 21:47     ` rostedt
2018-08-16 16:31 ` [PATCH v2 05/32] selftests/ftrace: More initialize features in initialize_ftrace Masami Hiramatsu
2018-08-16 16:31   ` Masami Hiramatsu
2018-08-16 16:31   ` mhiramat
2018-08-24 21:24   ` Steven Rostedt
2018-08-24 21:24     ` Steven Rostedt
2018-08-24 21:24     ` rostedt
2018-08-24 21:46   ` Steven Rostedt
2018-08-24 21:46     ` Steven Rostedt
2018-08-24 21:46     ` rostedt
2018-08-24 21:46     ` Steven Rostedt
2018-08-24 21:46       ` Steven Rostedt
2018-08-24 21:46       ` rostedt
2018-08-16 16:32 ` [PATCH v2 06/32] selftests/ftrace: Add SPDX License Identifier to template Masami Hiramatsu
2018-08-16 16:32   ` Masami Hiramatsu
2018-08-16 16:32   ` mhiramat
2018-08-16 16:32 ` [PATCH v2 07/32] selftests/ftrace: Cleanup ftrace after running test Masami Hiramatsu
2018-08-16 16:32   ` Masami Hiramatsu
2018-08-16 16:32   ` mhiramat
2018-08-16 16:32 ` [PATCH v2 08/32] selftests/ftrace: Remove unneeded per-test init/cleanup ftrace Masami Hiramatsu
2018-08-16 16:32   ` Masami Hiramatsu
2018-08-16 16:32   ` mhiramat
2018-08-16 16:33 ` [PATCH v2 09/32] selftests/ftrace: Fix to test kprobe $comm arg only if available Masami Hiramatsu
2018-08-16 16:33   ` Masami Hiramatsu
2018-08-16 16:33   ` mhiramat
2018-08-16 16:33 ` [PATCH v2 10/32] selftests/ftrace: Fix checkbashisms errors Masami Hiramatsu
2018-08-16 16:33   ` Masami Hiramatsu
2018-08-16 16:33   ` mhiramat
2018-08-24 21:50   ` Steven Rostedt
2018-08-24 21:50     ` Steven Rostedt
2018-08-24 21:50     ` rostedt
2018-08-16 16:34 ` [PATCH v2 11/32] selftests/ftrace: Use loopback address instead of localhost Masami Hiramatsu
2018-08-16 16:34   ` Masami Hiramatsu
2018-08-16 16:34   ` mhiramat
2018-08-24 21:52   ` Steven Rostedt
2018-08-24 21:52     ` Steven Rostedt
2018-08-24 21:52     ` rostedt
2018-08-25  1:47     ` Masami Hiramatsu
2018-08-25  1:47       ` Masami Hiramatsu
2018-08-25  1:47       ` mhiramat
2018-08-16 16:34 ` [PATCH v2 12/32] selftests/ftrace: Improve kprobe on module testcase to load/unload module Masami Hiramatsu
2018-08-16 16:34   ` Masami Hiramatsu
2018-08-16 16:34   ` mhiramat
2018-08-24 23:07   ` Steven Rostedt
2018-08-24 23:07     ` Steven Rostedt
2018-08-24 23:07     ` rostedt
2018-08-16 16:35 ` [PATCH v2 13/32] selftests/ftrace: Improve kprobe testcase to check log data Masami Hiramatsu
2018-08-16 16:35   ` Masami Hiramatsu
2018-08-16 16:35   ` mhiramat
2018-08-16 16:35 ` [PATCH v2 14/32] selftests/ftrace: Improve kretprobe " Masami Hiramatsu
2018-08-16 16:35   ` Masami Hiramatsu
2018-08-16 16:35   ` mhiramat
2018-08-16 16:36 ` [PATCH v2 15/32] selftests/ftrace: Test kprobe-event argument with various bitsize Masami Hiramatsu
2018-08-16 16:36   ` Masami Hiramatsu
2018-08-16 16:36   ` mhiramat
2018-08-16 16:36 ` [PATCH v2 16/32] selftests/ftrace: Check set_event_pid result Masami Hiramatsu
2018-08-16 16:36   ` Masami Hiramatsu
2018-08-16 16:36   ` mhiramat
2018-08-16 16:37 ` [PATCH v2 17/32] selftests/ftrace: Add kprobe event with $comm argument testcase Masami Hiramatsu
2018-08-16 16:37   ` Masami Hiramatsu
2018-08-16 16:37   ` mhiramat
2018-08-16 16:37 ` [PATCH v2 18/32] selftests/ftrace: Add kprobe profile testcase Masami Hiramatsu
2018-08-16 16:37   ` Masami Hiramatsu
2018-08-16 16:37   ` mhiramat
2018-08-16 16:38 ` [PATCH v2 19/32] selftests/ftrace: Add a testcase for nop tracer Masami Hiramatsu
2018-08-16 16:38   ` Masami Hiramatsu
2018-08-16 16:38   ` mhiramat
2018-08-24 22:53   ` Steven Rostedt
2018-08-24 22:53     ` Steven Rostedt
2018-08-24 22:53     ` rostedt
2018-08-26  7:30     ` Masami Hiramatsu
2018-08-26  7:30       ` Masami Hiramatsu
2018-08-26  7:30       ` mhiramat
2018-08-16 16:38 ` [PATCH v2 20/32] selftests/ftrace: Add kprobe-event with symbol argument test Masami Hiramatsu
2018-08-16 16:38   ` Masami Hiramatsu
2018-08-16 16:38   ` mhiramat
2018-08-16 16:39 ` [PATCH v2 21/32] selftests/ftrace: Add trace_printk sample module test Masami Hiramatsu
2018-08-16 16:39   ` Masami Hiramatsu
2018-08-16 16:39   ` mhiramat
2018-08-24 23:06   ` Steven Rostedt
2018-08-24 23:06     ` Steven Rostedt
2018-08-24 23:06     ` rostedt
2018-08-26  8:43     ` Masami Hiramatsu
2018-08-26  8:43       ` Masami Hiramatsu
2018-08-26  8:43       ` mhiramat
2018-08-16 16:39 ` [PATCH v2 22/32] selftests/ftrace: Add ringbuffer size changing testcase Masami Hiramatsu
2018-08-16 16:39   ` Masami Hiramatsu
2018-08-16 16:39   ` mhiramat
2018-08-24 23:18   ` Steven Rostedt
2018-08-24 23:18     ` Steven Rostedt
2018-08-24 23:18     ` rostedt
2018-08-30  7:12     ` Masami Hiramatsu
2018-08-30  7:12       ` Masami Hiramatsu
2018-08-30  7:12       ` mhiramat
2018-08-30 15:50       ` Steven Rostedt
2018-08-30 15:50         ` Steven Rostedt
2018-08-30 15:50         ` rostedt
2018-08-30 23:35         ` Masami Hiramatsu
2018-08-30 23:35           ` Masami Hiramatsu
2018-08-30 23:35           ` mhiramat
2018-08-30 23:40           ` Steven Rostedt
2018-08-30 23:40             ` Steven Rostedt
2018-08-30 23:40             ` rostedt
2018-08-16 16:40 ` [PATCH v2 23/32] selftests/ftrace: Add function profiling stat testcase Masami Hiramatsu
2018-08-16 16:40   ` Masami Hiramatsu
2018-08-16 16:40   ` mhiramat
2018-08-24 23:20   ` Steven Rostedt
2018-08-24 23:20     ` Steven Rostedt
2018-08-24 23:20     ` rostedt
2018-08-26 11:20     ` Masami Hiramatsu
2018-08-26 11:20       ` Masami Hiramatsu
2018-08-26 11:20       ` mhiramat
2018-08-16 16:40 ` [PATCH v2 24/32] selftests/ftrace: Add max stack tracer testcase Masami Hiramatsu
2018-08-16 16:40   ` Masami Hiramatsu
2018-08-16 16:40   ` mhiramat
2018-08-24 23:23   ` Steven Rostedt
2018-08-24 23:23     ` Steven Rostedt
2018-08-24 23:23     ` rostedt
2018-08-25  1:45     ` Masami Hiramatsu
2018-08-25  1:45       ` Masami Hiramatsu
2018-08-25  1:45       ` mhiramat
2018-08-25  2:41       ` Steven Rostedt
2018-08-25  2:41         ` Steven Rostedt
2018-08-25  2:41         ` rostedt
2018-08-26  8:42         ` Masami Hiramatsu
2018-08-26  8:42           ` Masami Hiramatsu
2018-08-26  8:42           ` mhiramat
2018-08-16 16:40 ` [PATCH v2 25/32] selftests/ftrace: Add function filter on module testcase Masami Hiramatsu
2018-08-16 16:40   ` Masami Hiramatsu
2018-08-16 16:40   ` mhiramat
2018-08-24 23:25   ` Steven Rostedt
2018-08-24 23:25     ` Steven Rostedt
2018-08-24 23:25     ` rostedt
2018-08-16 16:41 ` [PATCH v2 26/32] selftests/ftrace: Add trace_pipe testcase Masami Hiramatsu
2018-08-16 16:41   ` Masami Hiramatsu
2018-08-16 16:41   ` mhiramat
2018-08-24 23:26   ` Steven Rostedt
2018-08-24 23:26     ` Steven Rostedt
2018-08-24 23:26     ` rostedt
2018-08-26 11:20     ` Masami Hiramatsu
2018-08-26 11:20       ` Masami Hiramatsu
2018-08-26 11:20       ` mhiramat
2018-08-16 16:41 ` [PATCH v2 27/32] selftests/ftrace: Add stacktrace ftrace filter command testcase Masami Hiramatsu
2018-08-16 16:41   ` Masami Hiramatsu
2018-08-16 16:41   ` mhiramat
2018-08-24 23:28   ` Steven Rostedt
2018-08-24 23:28     ` Steven Rostedt
2018-08-24 23:28     ` rostedt
2018-08-16 16:42 ` [PATCH v2 28/32] selftests/ftrace: Add wakeup tracer testcase Masami Hiramatsu
2018-08-16 16:42   ` Masami Hiramatsu
2018-08-16 16:42   ` mhiramat
2018-08-16 16:42 ` [PATCH v2 29/32] selftests/ftrace: Add wakeup_rt " Masami Hiramatsu
2018-08-16 16:42   ` Masami Hiramatsu
2018-08-16 16:42   ` mhiramat
2018-08-25  2:09   ` Steven Rostedt
2018-08-25  2:09     ` Steven Rostedt
2018-08-25  2:09     ` rostedt
2018-08-26 11:22     ` Masami Hiramatsu
2018-08-26 11:22       ` Masami Hiramatsu
2018-08-26 11:22       ` mhiramat
2018-08-16 16:43 ` [PATCH v2 30/32] selftests/ftrace: Add ftrace cpumask testcase Masami Hiramatsu
2018-08-16 16:43   ` Masami Hiramatsu
2018-08-16 16:43   ` mhiramat
2018-08-25  2:18   ` Steven Rostedt [this message]
2018-08-25  2:18     ` Steven Rostedt
2018-08-25  2:18     ` rostedt
2018-08-27 12:16     ` Masami Hiramatsu
2018-08-27 12:16       ` Masami Hiramatsu
2018-08-27 12:16       ` mhiramat
2018-08-16 16:43 ` [PATCH v2 31/32] selftests/ftrace: Add output format testcase Masami Hiramatsu
2018-08-16 16:43   ` Masami Hiramatsu
2018-08-16 16:43   ` mhiramat
2018-08-25  2:19   ` Steven Rostedt
2018-08-25  2:19     ` Steven Rostedt
2018-08-25  2:19     ` rostedt
2018-08-30  7:48     ` Masami Hiramatsu
2018-08-30  7:48       ` Masami Hiramatsu
2018-08-30  7:48       ` mhiramat
2018-08-16 16:44 ` [PATCH v2 32/32] selftests/ftrace: Add blktrace testcase Masami Hiramatsu
2018-08-16 16:44   ` Masami Hiramatsu
2018-08-16 16:44   ` mhiramat
2018-08-25  2:22   ` Steven Rostedt
2018-08-25  2:22     ` Steven Rostedt
2018-08-25  2:22     ` rostedt
2018-08-30  7:53     ` Masami Hiramatsu
2018-08-30  7:53       ` Masami Hiramatsu
2018-08-30  7:53       ` mhiramat

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=20180824221822.3e0092c9@vmware.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=shuah@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.