Re: [RFC v1 01/11] core: Add btd_service to represent device services

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Mikel,

On Tue, Mar 26, 2013, Mikel Astiz wrote:
> +static const char *state2str(btd_service_state_t state)
> +{
> +	switch(state) {
> +	case BTD_SERVICE_STATE_UNAVAILABLE:
> +		return "BTD_SERVICE_STATE_UNAVAILABLE";
> +	case BTD_SERVICE_STATE_DISCONNECTED:
> +		return "BTD_SERVICE_STATE_DISCONNECTED";
> +	case BTD_SERVICE_STATE_CONNECTING:
> +		return "BTD_SERVICE_STATE_CONNECTING";
> +	case BTD_SERVICE_STATE_CONNECTED:
> +		return "BTD_SERVICE_STATE_CONNECTED";
> +	case BTD_SERVICE_STATE_DISCONNECTING:
> +		return "BTD_SERVICE_STATE_DISCONNECTING";
> +	}

Minor thing: Could you just make the strings "unavailable",
"disconnected", etc. The context is already evident from the rest of the
logs (especially the DBG ones) and having something shorter would make
them more readable.

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




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux