* linux-next: manual merge of the tip tree with the bluetooth tree
@ 2017-06-28 3:22 Stephen Rothwell
0 siblings, 0 replies; only message in thread
From: Stephen Rothwell @ 2017-06-28 3:22 UTC (permalink / raw)
To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra,
Gustavo Padovan
Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Jeffy Chen,
Marcel Holtmann
Hi all,
Today's linux-next merge of the tip tree got conflicts in:
net/bluetooth/bnep/core.c
net/bluetooth/cmtp/core.c
net/bluetooth/hidp/core.c
between commits:
25717382c1dd ("Bluetooth: bnep: fix possible might sleep error in bnep_session")
f06d977309d0 ("Bluetooth: cmtp: fix possible might sleep error in cmtp_session")
5da8e47d849d ("Bluetooth: hidp: fix possible might sleep error in hidp_session_thread")
from the bluetooth tree and commit:
ac6424b981bc ("sched/wait: Rename wait_queue_t => wait_queue_entry_t")
from the tip tree.
I fixed it up (the former changed the wait_queue_t declarations
to DEFINE_WAIT_FUNC(), so I used 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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-06-28 3:22 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-06-28 3:22 linux-next: manual merge of the tip tree with the bluetooth 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).