Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1569376 > unrolled thread
| Started by | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| First post | 2017-01-30 05:10 +0100 |
| Last post | 2017-01-30 05:10 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
linux-next: manual merge of the staging tree with the staging.current tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-01-30 05:10 +0100
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2017-01-30 05:10 +0100 |
| Subject | linux-next: manual merge of the staging tree with the staging.current tree |
| Message-ID | <t5brX-7KX-7@gated-at.bofh.it> |
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in:
drivers/staging/greybus/timesync_platform.c
between commit:
b17c1bba9cec ("staging: greybus: timesync: validate platform state callback")
from the staging.current tree and commit:
bdfb95c4baab ("staging: greybus: remove timesync protocol support")
from the staging tree.
I fixed it up (I just removed the file) 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