directly track bus <-> connection
update locking and tear-down logic at disconnect()
save the bus when we fiddle with the function paramter
connection: cancel work outside of bus lock
connection: pin the connection which scheduled work
connection: free notify list
endpoint: fix kerneldoc
connection: first ref() then unref() when moving references
replace work+timer with delayed_work
connection: merge kdbus_conn_msg_recv()
connection: send dead reply on KDBUS_RECV_DROP
connection: let conn->reply_list keep track of allowed replies

Currently, when connection A sends a message to connection B, we store
the reply item with connection A, indicating that connection B is
allowed to reply to connection A.

This creates an ABBA locking issue with MSG_DROP, as we have to hold
both locks in order to do the list_del(reply->entry).

Let's do it the other way around and let conn->reply_list store the
reply items of allowed replies *from* the connection instead. That also
simplifies a number of all sites, as we don't have to walk all
connection on the bus anymore in order to find out whether anyone is
waiting for a reply from us.
connection, kdbus_conn_disconnect: splice out reply list under lock

Then walk the list without the lock held.
kdbus_conn_move_messages: splice list of expected replies
release parent lock when disconnecting children objects
update marketing text
connection: follow new reply_list logic in kdbus_cmd_msg_cancel
connection: walk remote lists in kdbus_cmd_msg_cancel

This partly reverts commit 4ff527c2, but fixes the list entry
logic that was broken before.
fix URL
connection: do not re-schedule work for a disconncted connection