Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1570371 > unrolled thread
| Started by | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| First post | 2017-01-31 06:50 +0100 |
| Last post | 2017-01-31 06:50 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
linux-next: manual merge of the pinctrl tree with the arm-soc tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-01-31 06:50 +0100
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2017-01-31 06:50 +0100 |
| Subject | linux-next: manual merge of the pinctrl tree with the arm-soc tree |
| Message-ID | <t5zuk-5gO-77@gated-at.bofh.it> |
Hi Linus,
Today's linux-next merge of the pinctrl tree got a conflict in:
arch/arm/mach-exynos/suspend.c
between commit:
b4765037fc8c ("ARM: EXYNOS: Constify list of retention registers")
from the arm-soc tree and commit:
07731019c59c ("pinctrl: samsung: Move retention control from mach-exynos to the pinctrl driver")
from the pinctrl tree.
I fixed it up (the latter removed the code updated by the former, so I
just did that) 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
Back to top | Article view | linux.kernel
csiph-web