linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>, "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Brian Norris <briannorris@chromium.org>
Subject: linux-next: manual merge of the driver-core tree with the pm tree
Date: Mon, 14 Nov 2016 13:09:02 +1100	[thread overview]
Message-ID: <20161114130902.532c3c64@canb.auug.org.au> (raw)

Hi Greg,

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

  drivers/base/power/main.c

between commit:

  6f75c3fd56da ("PM / sleep: don't suspend parent when async child suspend_{noirq, late} fails")

from the pm tree and commit:

  8c73b4288496 ("PM / sleep: Make async suspend/resume of devices use device links")

from the driver-core tree.

I fixed it up (maybe .. 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 drivers/base/power/main.c
index 2932a5bd892f,04bcb11ed8de..000000000000
--- a/drivers/base/power/main.c
+++ b/drivers/base/power/main.c
@@@ -1027,8 -1085,6 +1085,8 @@@ static int __device_suspend_noirq(struc
  	TRACE_DEVICE(dev);
  	TRACE_SUSPEND(0);
  
- 	dpm_wait_for_children(dev, async);
++	dpm_wait_for_subordinate(dev, async);
 +
  	if (async_error)
  		goto Complete;
  
@@@ -1174,8 -1232,6 +1232,8 @@@ static int __device_suspend_late(struc
  
  	__pm_runtime_disable(dev, false);
  
- 	dpm_wait_for_children(dev, async);
++	dpm_wait_for_subordinate(dev, async);
 +
  	if (async_error)
  		goto Complete;
  

             reply	other threads:[~2016-11-14  2:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14  2:09 Stephen Rothwell [this message]
2016-11-14 21:07 ` linux-next: manual merge of the driver-core tree with the pm tree Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2019-07-01  8:32 Stephen Rothwell
2019-07-03 13:04 ` Andy Shevchenko
2018-12-10  5:14 Stephen Rothwell
2018-12-10  8:58 ` Rafael J. Wysocki
2018-12-10  9:02   ` Andy Shevchenko
2014-11-11  4:41 Stephen Rothwell
2014-12-02 18:10 ` Greg KH
2014-11-10  4:18 Stephen Rothwell
2014-11-10  4:40 ` Greg KH
2013-08-30  5:26 Stephen Rothwell
2013-08-30  6:02 ` Greg KH
2013-06-27  7:14 Stephen Rothwell
2013-06-27 15:36 ` Greg KH
2013-06-07  4:49 Stephen Rothwell
2013-06-07 17:38 ` Greg KH
2013-05-22  3:47 Stephen Rothwell
2013-05-22  4:02 ` Stephen Rothwell
2013-05-22 11:26   ` Rafael J. Wysocki
2013-02-11  4:42 Stephen Rothwell
2013-02-11 12:10 ` Rafael J. Wysocki

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=20161114130902.532c3c64@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=briannorris@chromium.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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;
as well as URLs for NNTP newsgroup(s).