From: Szymon Janc <szymon.janc@tieto.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] gdbus: Use g_dbus_create_error_valist internally
Date: Thu, 09 Apr 2015 16:39:32 +0200 [thread overview]
Message-ID: <1504839.97hPZ0nfai@leonov> (raw)
In-Reply-To: <1428437449-11210-1-git-send-email-szymon.janc@tieto.com>
On Tuesday 07 of April 2015 22:10:48 Szymon Janc wrote:
> There is no need to duplicate code in g_dbus_send_error_valist.
> ---
> gdbus/object.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/gdbus/object.c b/gdbus/object.c
> index 4d5a64c..c3c137b 100644
> --- a/gdbus/object.c
> +++ b/gdbus/object.c
> @@ -1530,11 +1530,8 @@ gboolean g_dbus_send_error_valist(DBusConnection
> *connection, const char *format, va_list args)
> {
> DBusMessage *error;
> - char str[1024];
> -
> - vsnprintf(str, sizeof(str), format, args);
>
> - error = dbus_message_new_error(message, name, str);
> + error = g_dbus_create_error_valist(message, name, format, args);
> if (error == NULL)
> return FALSE;
Applied.
--
BR
Szymon Janc
prev parent reply other threads:[~2015-04-09 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 20:10 [PATCH 1/2] gdbus: Use g_dbus_create_error_valist internally Szymon Janc
2015-04-07 20:10 ` [PATCH 2/2] gdbus: Fix crash in g_dbus_create_error_valist Szymon Janc
2015-04-09 14:39 ` Szymon Janc [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1504839.97hPZ0nfai@leonov \
--to=szymon.janc@tieto.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox