From: "michal.lowas-rzechonek@silvair.com" <michal.lowas-rzechonek@silvair.com>
To: "Gix, Brian" <brian.gix@intel.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ] mesh: Log D-Bus method call errors
Date: Fri, 30 Aug 2019 07:47:52 +0200 [thread overview]
Message-ID: <20190830054752.o3wrahabdsqmmvrt@kynes> (raw)
In-Reply-To: <38E88E55-4291-47AF-B502-47922E9FBA56@intel.com>
Brian,
On 08/29, Gix, Brian wrote:
> > Anyway, I think a better approach would be to submit patches to ELL
> > implementing these two features, and then use these additions in meshd.
> > Does that sound acceptable from your POV?
>
> I still feel though, that you are trying to solve a pre-deployment
> “debugging” issue by requiring DBus responses for messages that don’t
> require them.
I think you're right.
Let's drop this patch, and I'll try to come up with something that would
cover only "important" methods you mentioned earlier.
regards
--
Michał Lowas-Rzechonek <michal.lowas-rzechonek@silvair.com>
Silvair http://silvair.com
Jasnogórska 44, 31-358 Krakow, POLAND
prev parent reply other threads:[~2019-08-30 5:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 7:56 [PATCH BlueZ] mesh: Log D-Bus method call errors Michał Lowas-Rzechonek
2019-08-28 16:22 ` Gix, Brian
2019-08-29 9:59 ` michal.lowas-rzechonek
2019-08-29 18:38 ` Gix, Brian
2019-08-29 19:56 ` michal.lowas-rzechonek
2019-08-29 20:07 ` Gix, Brian
2019-08-30 5:47 ` michal.lowas-rzechonek [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=20190830054752.o3wrahabdsqmmvrt@kynes \
--to=michal.lowas-rzechonek@silvair.com \
--cc=brian.gix@intel.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;
as well as URLs for NNTP newsgroup(s).