Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 30 Aug 2019 07:47:52 +0200
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
Message-ID: <20190830054752.o3wrahabdsqmmvrt@kynes>
Mail-Followup-To: "Gix, Brian" <brian.gix@intel.com>,
        "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
References: <20190820075654.2195-1-michal.lowas-rzechonek@silvair.com>
 <685bc703108f5329b861f5c5f87301b44bddd8e0.camel@intel.com>
 <20190829095951.nzzqqhgvblhogf4e@mlowasrzechonek2133>
 <145b9b726c45fd37592b5a7a3504c911cd848409.camel@intel.com>
 <20190829195610.a6dwgxabq3d2g3bp@kynes>
 <38E88E55-4291-47AF-B502-47922E9FBA56@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <38E88E55-4291-47AF-B502-47922E9FBA56@intel.com>
User-Agent: NeoMutt/20180716
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

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