From: "Paul E. McKenney" <paulmck@kernel.org>
To: Jules Irenge <jbi.octave@gmail.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, boqun.feng@gmail.com
Subject: Re: [PATCH 0/5] cleanups
Date: Tue, 2 Jun 2020 09:45:10 -0700 [thread overview]
Message-ID: <20200602164510.GH29598@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200601184552.23128-1-jbi.octave@gmail.com>
On Mon, Jun 01, 2020 at 07:45:47PM +0100, Jules Irenge wrote:
>
> Jules Irenge (5):
> rcu/rcutorture: replace 0 with false
> rcu: replace 1 with true
I queued these two, thank you!
> rcu: replace + with |
This one I am not all that excited about, so I am leaving it off.
Thanx, Paul
> x86/ftrace: Add annotations for ftrace_arch_code_modify_prepare() and
> ftrace_arch_code_modify_post_process()
> sfc: add missing annotation for efx_ef10_try_update_nic_stats_vf()
>
> arch/x86/kernel/ftrace.c | 2 ++
> drivers/net/ethernet/sfc/ef10.c | 1 +
> kernel/rcu/rcutorture.c | 2 +-
> kernel/rcu/tree_plugin.h | 22 +++++++++++-----------
> kernel/rcu/update.c | 2 +-
> 5 files changed, 16 insertions(+), 13 deletions(-)
>
> --
> 2.18.2
>
next prev parent reply other threads:[~2020-06-02 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 18:45 [PATCH 0/5] cleanups Jules Irenge
2020-06-01 18:45 ` [PATCH 1/5] rcu/rcutorture: replace 0 with false Jules Irenge
2020-06-01 18:45 ` [PATCH 2/5] rcu: replace 1 with true Jules Irenge
2020-06-01 18:45 ` [PATCH 3/5] rcu: replace + with | Jules Irenge
2020-06-01 18:45 ` [PATCH 4/5] x86/ftrace: Add annotations for ftrace_arch_code_modify_prepare() and ftrace_arch_code_modify_post_process() Jules Irenge
2020-06-01 19:46 ` Steven Rostedt
2020-06-01 22:01 ` ý€€€„
2020-06-02 23:10 ` Luc Van Oostenryck
2020-06-05 7:42 ` ý€€€„
2020-06-01 18:45 ` [PATCH 5/5] sfc: add missing annotation for efx_ef10_try_update_nic_stats_vf() Jules Irenge
2020-06-01 22:52 ` David Miller
2020-06-02 16:45 ` Paul E. McKenney [this message]
2020-06-05 7:45 ` [PATCH 0/5] cleanups ý€€€„
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=20200602164510.GH29598@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=jbi.octave@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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