All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ell@lists.01.org
Subject: Re: [PATCH 01/12] dbus: Kdbus message timeout_ns is absolute time
Date: Mon, 11 Apr 2016 14:42:10 -0500	[thread overview]
Message-ID: <570BFE12.4010602@gmail.com> (raw)
In-Reply-To: <1460260961-9183-1-git-send-email-andrew.zaborowski@intel.com>

[-- Attachment #1: Type: text/plain, Size: 345 bytes --]

Hi Andrew,

On 04/09/2016 11:02 PM, Andrew Zaborowski wrote:
> It is even documented in systemd, although not very clearly, that
> timeout_ns is a CLOCK_MONOTONIC_COARSE-based absolute value.
> ---
>   ell/dbus-kernel.c | 13 +++++++++++--
>   1 file changed, 11 insertions(+), 2 deletions(-)
>

Applied, thanks.

Regards,
-Denis


      parent reply	other threads:[~2016-04-11 19:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-10  4:02 [PATCH 01/12] dbus: Kdbus message timeout_ns is absolute time Andrew Zaborowski
2016-04-10  4:02 ` [PATCH 02/12] dbus: Validate field type in get_header_field Andrew Zaborowski
2016-04-11 20:00   ` Denis Kenzior
2016-04-11 20:06     ` Andrzej Zaborowski
2016-04-10  4:02 ` [PATCH 03/12] dbus: Check some more return values when parsing messages Andrew Zaborowski
2016-04-11 20:11   ` Denis Kenzior
2016-04-12  1:23     ` Andrzej Zaborowski
2016-04-10  4:02 ` [PATCH 04/12] dbus: GVariant header field identifiers are 64-bit Andrew Zaborowski
2016-04-10  4:02 ` [PATCH 05/12] dbus: Fix parsing GVariant header/body information Andrew Zaborowski
2016-04-10  4:02 ` [PATCH 06/12] dbus: GVariant message cookie and reply cookie are 64-bit Andrew Zaborowski
2016-04-10  4:02 ` [PATCH 07/12] dbus: Don't rely on 1st KDBUS_ITEM_PAYLOAD_OFF being the header Andrew Zaborowski
2016-04-10  4:02 ` [PATCH 08/12] gvariant: Utility to build GVariant message out of header+body Andrew Zaborowski
2016-04-10  4:02 ` [PATCH 09/12] dbus: Fix the kdbus message encoding Andrew Zaborowski
2016-04-11 19:42 ` Denis Kenzior [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=570BFE12.4010602@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ell@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.