Fine with me. Pushed. --Jason Ekstrand
On Thu, Jul 24, 2014 at 5:35 PM, Bryce W. Harrington < [email protected]> wrote: > Use function linking syntax instead of variable linking, to resolve two > warnings: > > wayland-server.h:167: warning: explicit link request to > 'wl_list_remove' could not be resolved > wayland-server.h:188: warning: explicit link request to > 'wl_list_remove' could not be resolved > > Signed-off-by: Bryce Harrington <[email protected]> > --- > src/wayland-server.h | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/src/wayland-server.h b/src/wayland-server.h > index 7fc5b47..0a3f2f6 100644 > --- a/src/wayland-server.h > +++ b/src/wayland-server.h > @@ -168,7 +168,7 @@ wl_client_post_no_memory(struct wl_client *client); > * } > * \endcode > * > - * If you need to remove a listener from a signal, use #wl_list_remove. > + * If you need to remove a listener from a signal, use wl_list_remove(). > * > * \code > * wl_list_remove(&your_listener.link); > @@ -189,7 +189,7 @@ struct wl_listener { > * Compositors as well as the server can provide signals. Observers are > * wl_listener's that are added through #wl_signal_add. Signals are > emitted > * using #wl_signal_emit, which will invoke all listeners until that > - * listener is removed by #wl_list_remove (or whenever the signal is > + * listener is removed by wl_list_remove() (or whenever the signal is > * destroyed). > * > * \sa wl_listener for more information on using wl_signal > -- > 1.7.9.5 > _______________________________________________ > wayland-devel mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/wayland-devel >
_______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
