public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Steven Rostedt <rostedt@goodmis.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: manual merge of the rcu tree with the ftrace tree
Date: Mon, 1 May 2017 13:18:51 +1000	[thread overview]
Message-ID: <20170501131851.677c8799@canb.auug.org.au> (raw)

Hi Paul,

Today's linux-next merge of the rcu tree got a conflict in:

  kernel/rcu/tree.c

between commit:

  a278d4718988 ("rcu: Fix dyntick-idle tracing")

from the ftrace tree and commit:

  e83d58dc7de2 ("rcu: Add lockdep_assert_held() teeth to tree.c")

from the rcu tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc kernel/rcu/tree.c
index ea2da0b22a6f,e180eea5061e..000000000000
--- a/kernel/rcu/tree.c
+++ b/kernel/rcu/tree.c
@@@ -792,9 -785,10 +799,10 @@@ static void rcu_eqs_enter_common(bool u
  {
  	struct rcu_state *rsp;
  	struct rcu_data *rdp;
 -	RCU_TRACE(struct rcu_dynticks *rdtp = this_cpu_ptr(&rcu_dynticks);)
 +	struct rcu_dynticks *rdtp = this_cpu_ptr(&rcu_dynticks);
  
+ 	RCU_LOCKDEP_WARN(!irqs_disabled(), "rcu_eqs_enter_common() invoked with irqs enabled!!!");
 -	trace_rcu_dyntick(TPS("Start"), oldval, rdtp->dynticks_nesting);
 +	trace_rcu_dyntick(TPS("Start"), rdtp->dynticks_nesting, 0);
  	if (IS_ENABLED(CONFIG_RCU_EQS_DEBUG) &&
  	    !user && !is_idle_task(current)) {
  		struct task_struct *idle __maybe_unused =

             reply	other threads:[~2017-05-01  3:18 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-01  3:18 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-06  1:24 linux-next: manual merge of the rcu tree with the ftrace tree Stephen Rothwell
2025-11-14  2:52 Stephen Rothwell
2025-11-14 12:42 ` Steven Rostedt
2025-11-14 13:35   ` Sebastian Andrzej Siewior
2025-11-14 15:46     ` Steven Rostedt
2025-11-14 16:00       ` Sebastian Andrzej Siewior
2025-11-14 16:22         ` Steven Rostedt
2025-11-14 16:33           ` Sebastian Andrzej Siewior
2025-11-14 16:48             ` Steven Rostedt
2025-11-14 17:02               ` Sebastian Andrzej Siewior
2025-11-14 17:11                 ` Steven Rostedt
2025-11-14 17:00             ` Paul E. McKenney
2025-11-14 17:10               ` Sebastian Andrzej Siewior
2025-11-14 17:25                 ` Paul E. McKenney
2025-11-14 17:40                   ` Steven Rostedt
2025-11-14 17:41                   ` Sebastian Andrzej Siewior
2025-11-14 18:26                     ` Paul E. McKenney
2025-11-14 14:48   ` Frederic Weisbecker
2025-11-14 16:01     ` Steven Rostedt
2025-11-14 17:06     ` Paul E. McKenney
2025-11-14 18:58       ` Paul E. McKenney
2025-11-18 13:05       ` Frederic Weisbecker
2025-11-18 15:04         ` Paul E. McKenney
2025-12-02  0:57           ` Paul E. McKenney
2025-12-07 20:43             ` Paul E. McKenney
2025-12-08  0:17               ` Steven Rostedt
2025-12-08  4:21                 ` Paul E. McKenney
2025-11-14 17:05   ` Paul E. McKenney
2025-11-14 18:31     ` Yonghong Song
2025-11-18  7:35       ` Sebastian Andrzej Siewior
2025-11-18 15:05         ` Paul E. McKenney
2025-11-30 18:49         ` Yonghong Song
2025-11-19  0:38     ` Paul E. McKenney

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=20170501131851.677c8799@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox