From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 1/2] rcu/tree: handle VM stoppage in stall detection
Date: Thu, 15 Jul 2021 23:08:41 +0900 [thread overview]
Message-ID: <YPBBaSnoGSeQtawz@google.com> (raw)
In-Reply-To: <20210715133241.GJ4397@paulmck-ThinkPad-P17-Gen-1>
On (21/07/15 06:32), Paul E. McKenney wrote:
> >
> > Hello Paul,
> >
> > I've noticed that this patch set didn't make it to Linus's tree.
> > Was it intentional?
>
> This patch (and the 18 preceding it) didn't make the cutoff for the
> just-past merge window.
Oh, I see.
> If this patch is urgent, please let me know
> and I can push it, with luck by the end of next week.
>
> If that one is urgent, are these two also?
No, Paul, nothing is urgent.
Many thanks for the detailed clarifications.
prev parent reply other threads:[~2021-07-15 14:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 15:56 [PATCHv2 1/2] rcu/tree: handle VM stoppage in stall detection Sergey Senozhatsky
2021-05-21 15:56 ` [PATCH 2/2] rcu: do not disable gp stall detection in rcu_cpu_stall_reset() Sergey Senozhatsky
2021-05-21 18:01 ` [PATCHv2 1/2] rcu/tree: handle VM stoppage in stall detection Paul E. McKenney
2021-05-21 21:38 ` Paul E. McKenney
2021-05-24 1:56 ` Sergey Senozhatsky
2021-05-24 3:46 ` Paul E. McKenney
2021-05-24 4:00 ` Sergey Senozhatsky
2021-07-15 9:09 ` Sergey Senozhatsky
2021-07-15 13:32 ` Paul E. McKenney
2021-07-15 14:08 ` Sergey Senozhatsky [this message]
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=YPBBaSnoGSeQtawz@google.com \
--to=senozhatsky@chromium.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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.