From 2c47fff6d2d9750ddf9e97fc45714aa8984b5eb6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Fri, 27 Jul 2018 08:06:07 +0200 Subject: [PATCH] man: clarify what can be NULL in an sd_bus_unrefp call Confusingly, the argument is called 'bus' in all cases. Let's not give people the idea to call sd_bus_unrefp(NULL). --- man/sd_bus_new.xml | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/man/sd_bus_new.xml b/man/sd_bus_new.xml index b095518f8f..5180ae7815 100644 --- a/man/sd_bus_new.xml +++ b/man/sd_bus_new.xml @@ -48,7 +48,7 @@ void sd_bus_unrefp - sd_bus **bus + sd_bus **busp @@ -105,10 +105,12 @@ … } - sd_bus_ref(), - sd_bus_unref() and - sd_bus_unrefp() execute no operation if the - passed in bus object is NULL. + sd_bus_ref() and sd_bus_unref() + execute no operation if the passed in bus object address is + NULL. sd_bus_unrefp() will first + dereference its argument, which must not be NULL, and will + execute no operation if that is NULL. +