Hi Grzegorz,
> This is needed if user space wants to know supported bnep features
> by kernel, eg. if kernel supports sending response to bnep setup
> control message.
>
> Signed-off-by: Grzegorz Kolodziejczyk <grzegorz.kolodziejczyk@xxxxxxxxx>
> ---
> net/bluetooth/bnep/bnep.h | 4 ++++
> net/bluetooth/bnep/sock.c | 8 ++++++++
> 2 files changed, 12 insertions(+)
>
> diff --git a/net/bluetooth/bnep/bnep.h b/net/bluetooth/bnep/bnep.h
> index 5a5b16f..a116e2e 100644
> --- a/net/bluetooth/bnep/bnep.h
> +++ b/net/bluetooth/bnep/bnep.h
> @@ -80,6 +80,9 @@
> #define BNEP_TYPE_MASK 0x7f
> #define BNEP_EXT_HEADER 0x80
>
> +/* Flags */
> +#define BNEP_SETUP_RSP_FLAG 0x00000000
> +
> struct bnep_setup_conn_req {
> __u8 type;
> __u8 ctrl;
> @@ -111,6 +114,7 @@ struct bnep_ext_hdr {
> #define BNEPCONNDEL _IOW('B', 201, int)
> #define BNEPGETCONNLIST _IOR('B', 210, int)
> #define BNEPGETCONNINFO _IOR('B', 211, int)
> +#define BNEPGETSUPPFEAT _IOR('B', 212, int)
as mentioned on IRC, you forgot compat_ioctl.h
> struct bnep_connadd_req {
> int sock; /* Connected socket */
> diff --git a/net/bluetooth/bnep/sock.c b/net/bluetooth/bnep/sock.c
> index 5f05129..6b84baf 100644
> --- a/net/bluetooth/bnep/sock.c
> +++ b/net/bluetooth/bnep/sock.c
> @@ -29,6 +29,8 @@
>
> #include "bnep.h"
>
> +static const __u32 supp_feat = BIT(BNEP_SETUP_RSP_FLAG);
> +
I am confused with the naming here. Are we exposing current state or supported features or what?
Regards
Marcel
--
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
