All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Steven Rostedt (VMware)" <rostedt@goodmis.org>
Subject: Re: linux-next: manual merge of the rcu tree with Linus' tree
Date: Mon, 25 Sep 2017 20:26:28 -0700	[thread overview]
Message-ID: <20170926032628.GT3521@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170926130018.421ed780@canb.auug.org.au>

On Tue, Sep 26, 2017 at 01:00:18PM +1000, Stephen Rothwell wrote:
> Hi Paul,
> 
> Today's linux-next merge of the rcu tree got a conflict in:
> 
>   kernel/rcu/tree.c
> 
> between commit:
> 
>   28585a832602 ("rcu: Allow for page faults in NMI handlers")
> 
> from Linus' tree and commit:
> 
>   3e2baa988b9c ("rcu: Allow for page faults in NMI handlers")
> 
> from the rcu tree.
> 
> I fixed it up (I just used the rcu tree version) 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.

Hello, Stephen,

This conflict will disappear tomorrow, as I have merged the commit
from Linus's tree in place of mine and have added another commit that 
removes the READ_ONCE()s.  Same result, but no conflict.  ;-)

							Thanx, Paul

  reply	other threads:[~2017-09-26  3:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-26  3:00 linux-next: manual merge of the rcu tree with Linus' tree Stephen Rothwell
2017-09-26  3:26 ` Paul E. McKenney [this message]
2017-09-26  3:42   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2022-10-17 22:41 Stephen Rothwell
2022-10-18 18:38 ` Paul E. McKenney
2022-07-08  4:12 Stephen Rothwell
2022-07-08 15:23 ` Paul E. McKenney
2018-06-12  0:46 Stephen Rothwell
2018-06-12  1:01 ` Paul E. McKenney
2018-06-18  3:48 ` Stephen Rothwell
2018-06-18  3:49   ` Stephen Rothwell
2018-06-18 14:48     ` Paul E. McKenney
2018-05-14  3:46 Stephen Rothwell
2018-05-15 17:44 ` Paul E. McKenney
2017-03-08  0:46 Stephen Rothwell
2017-03-08  0:56 ` Stephen Rothwell
2016-03-30  0:32 Stephen Rothwell
2016-03-30 10:30 ` Paul E. McKenney
2016-03-30  0:23 Stephen Rothwell
2012-11-29  3:06 Stephen Rothwell
2012-11-29 22:12 ` Paul E. McKenney
2012-08-06  2:31 Stephen Rothwell
2011-09-27  6:04 Stephen Rothwell
2011-09-27 12:20 ` Frederic Weisbecker
2011-09-27  5:14 Stephen Rothwell
2011-09-27 13:14 ` Borislav Petkov
2010-10-06  2:38 Stephen Rothwell
2010-10-06  4:17 ` 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=20170926032628.GT3521@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sfr@canb.auug.org.au \
    /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.