Hi Bartosz, On Thu, Dec 08, 2011, Bartosz Szatkowski wrote: > --- > client/map.c | 56 ++++++++++++++++++++++++++++++++++++++++++++++++++++ > doc/client-api.txt | 5 +++- > 2 files changed, 60 insertions(+), 1 deletions(-) The first two patches have been applied, but this had issues: > +#define ERROR_INF MAP_INTERFACE ".Error" > +#define ERROR_FAILED_PATH "org.openobex.Error.Failed" First of all, this is not a path or an interface. It's the error name. Secondly, do you really need these defines since in some places you spell out the name inline in others you use a define. E.g. here it's inline: > + else if (err_code != G_OBEX_RSP_SUCCESS) > + reply = g_dbus_create_error(map->msg, > + "org.openobex.Error.Response", > + "%s (0x%02x)", > + g_obex_strerror(err_code), > + err_code); So please be consistent. Also think about whether we need MAP specific errors at all or if we can just use generic ones for the entire client (and maybe server too). Johan -- 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
