From: "Gix, Brian" <brian.gix@intel.com>
To: "michal.lowas-rzechonek@silvair.com"
<michal.lowas-rzechonek@silvair.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH BlueZ v2] mesh: Add deferral of Attach() and Leave() if busy
Date: Thu, 18 Jun 2020 15:48:56 +0000 [thread overview]
Message-ID: <12a59828baabec5621917d283e03338d796715f3.camel@intel.com> (raw)
In-Reply-To: <20200618154325.eaudqfy4inbjl7oy@kynes>
Hi Michał,
On Thu, 2020-06-18 at 17:43 +0200, michal.lowas-rzechonek@silvair.com wrote:
> On 06/18, Gix, Brian wrote:
> > Applied
>
> I have a vague impression that my comments about (void*) true have been
> ignored ;)
Sorry, I thought I had responded to this...
I am using the user_data for the Attach and Leave call (which the dbus system always passes as NULL) as the
indication that the timed deferral call is just that... Otherwise if we *never* get the JoinComplete
response, we will forever loop repeatedly re-deferring the Attach/Leave.
If we have already deferred the Attach/Leave, I still want to respond "Busy" to the App... because the App is
doing something wrong.... It owes us a response.
next prev parent reply other threads:[~2020-06-18 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 18:14 [PATCH BlueZ v2] mesh: Add deferral of Attach() and Leave() if busy Brian Gix
2020-06-17 7:50 ` Michał Lowas-Rzechonek
2020-06-18 15:41 ` Gix, Brian
2020-06-18 15:43 ` michal.lowas-rzechonek
2020-06-18 15:48 ` Gix, Brian [this message]
2020-06-18 15:54 ` michal.lowas-rzechonek
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=12a59828baabec5621917d283e03338d796715f3.camel@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michal.lowas-rzechonek@silvair.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