From: Daniel Wagner <wagi@monom.org>
To: Santtu Lakkala <santtu.lakkala@jolla.com>
Cc: Jussi Laakkonen <jussi.laakkonen@jolla.com>, connman@lists.linux.dev
Subject: Re: [PATCH v2 1/2] vpn-provider: Implement connmand online state checking
Date: Thu, 19 Aug 2021 15:06:16 +0200 [thread overview]
Message-ID: <20210819130616.gtdymlno5fmbi54j@carbon.lan> (raw)
In-Reply-To: <7f49edf3-75eb-3295-cc12-ae21faa903d8@jolla.com>
On Thu, Aug 19, 2021 at 03:38:08PM +0300, Santtu Lakkala wrote:
> On 19.8.2021 15.30, Daniel Wagner wrote:
> > BTW, the question on the busy loop. I am pretty sure there is no timeout
> > involved if you just return 'continue'. This tells the caller to queue
> > up the callback again without any delay.
>
> Nope, it called again after the same interval that was passed during
> construction.
Ah, okay, faulty memory here it seems. Anyway, thanks for
explaining.
next prev parent reply other threads:[~2021-08-19 13:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 15:14 [PATCH 0/2] Implement connmand state monitoring to vpnd Jussi Laakkonen
2021-08-17 15:14 ` [PATCH 1/2] vpn-provider: Implement connmand online state checking Jussi Laakkonen
2021-08-17 16:55 ` Daniel Wagner
2021-08-18 9:21 ` Jussi Laakkonen
2021-08-18 10:31 ` [PATCH v2 " Jussi Laakkonen
2021-08-19 12:11 ` Jussi Laakkonen
2021-08-19 12:30 ` Daniel Wagner
2021-08-19 12:38 ` Santtu Lakkala
2021-08-19 13:06 ` Daniel Wagner [this message]
2021-08-19 12:40 ` Jussi Laakkonen
2021-08-29 18:27 ` Daniel Wagner
2021-08-30 6:59 ` Jussi Laakkonen
2021-08-30 8:11 ` Daniel Wagner
2021-08-20 13:05 ` [PATCH v3 " Jussi Laakkonen
2021-08-17 15:14 ` [PATCH 2/2] vpn: Handle ENOLINK error in connect callback Jussi Laakkonen
2021-08-20 13:06 ` [PATCH v2 2/2] vpn: Refactor connect_reply() and handle NoCarrier -> ENOLINK error Jussi Laakkonen
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=20210819130616.gtdymlno5fmbi54j@carbon.lan \
--to=wagi@monom.org \
--cc=connman@lists.linux.dev \
--cc=jussi.laakkonen@jolla.com \
--cc=santtu.lakkala@jolla.com \
/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;
as well as URLs for NNTP newsgroup(s).