linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: manual merge of the pm tree with the renesas tree
@ 2016-04-26  1:52 Stephen Rothwell
  0 siblings, 0 replies; only message in thread
From: Stephen Rothwell @ 2016-04-26  1:52 UTC (permalink / raw)
  To: Rafael J. Wysocki, Simon Horman
  Cc: linux-next, linux-kernel, Geert Uytterhoeven, Viresh Kumar

Hi Rafael,

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

  arch/arm/mach-shmobile/Makefile

between commit:

  be32bcbbd182 ("soc: renesas: Move pm-rcar to drivers/soc/renesas/rcar-sysc")

from the renesas tree and commit:

  a399dc9fc500 ("cpufreq: shmobile: Use generic platdev driver")

from the pm 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 arch/arm/mach-shmobile/Makefile
index ebb909c55b85,c9ea0e6ff4f9..000000000000
--- a/arch/arm/mach-shmobile/Makefile
+++ b/arch/arm/mach-shmobile/Makefile
@@@ -38,7 -38,7 +38,6 @@@ smp-$(CONFIG_ARCH_EMEV2)	+= smp-emev2.
  
  # PM objects
  obj-$(CONFIG_SUSPEND)		+= suspend.o
- obj-$(CONFIG_CPU_FREQ)		+= cpufreq.o
 -obj-$(CONFIG_PM_RCAR)		+= pm-rcar.o
  obj-$(CONFIG_PM_RMOBILE)	+= pm-rmobile.o
  obj-$(CONFIG_ARCH_RCAR_GEN2)	+= pm-rcar-gen2.o
  

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2016-04-26  1:52 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-04-26  1:52 linux-next: manual merge of the pm tree with the renesas tree Stephen Rothwell

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).