[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190813142259.GZ28441@linux.ibm.com>
Date: Tue, 13 Aug 2019 07:22:59 -0700
From: "Paul E. McKenney" <paulmck@...ux.ibm.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Greg KH <greg@...ah.com>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Joel Fernandes (Google)" <joel@...lfernandes.org>
Subject: Re: linux-next: manual merge of the driver-core tree with the rcu
tree
On Tue, Aug 13, 2019 at 10:50:05AM +0200, Rafael J. Wysocki wrote:
> On 8/13/2019 7:50 AM, Stephen Rothwell wrote:
> >Hi all,
> >
> >Today's linux-next merge of the driver-core tree got a conflict in:
> >
> > drivers/base/power/runtime.c
> >
> >between commit:
> >
> > 4a3a5474b4c1 ("driver/core: Convert to use built-in RCU list checking")
> >
> >from the rcu tree and commit:
> >
> > 515db266a9da ("driver core: Remove device link creation limitation")
> >
> >from the driver-core 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.
> >
> The fix looks good to me, thanks!
Same here, and thank you!
Thanx, Paul
Powered by blists - more mailing lists