Hi Johan, Luiz, On Wed, Dec 12, 2012 at 1:02 PM, Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote: > Hi Luiz, > > On Wed, Dec 12, 2012, Luiz Augusto von Dentz wrote: >> This changes obexd to use ProfileManager.RegisterProfile >> --- >> obexd/plugins/bluetooth.c | 696 ++++++++++++++-------------------------------- >> 1 file changed, 212 insertions(+), 484 deletions(-) > > All patches in this set have been applied. I also removed the service > plugin in the same go as now all known users of it are gone. I'm a bit confused with these recent changes. I haven't been following this closely so I guess I'm missing the Big Plan but let me start with the basics: both bluetoothd and obexd repositories were merged but I believe both daemons are still going to be separate daemons, is this correct? If yes, it makes sense that obexd makes use of the "external profile" infrastructure. But in that case, why would we add any obex-specific code into bluetoothd? My understanding was that, if a profile is implemented as an external profile, the bluetoothd core would not be aware of it. Cheers, Mikel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
