On Wed, 27 May 2009 18:05:13 -0700
Inaky Perez-Gonzalez <inaky@linux.intel.com> wrote:

quoted text
> From: Paulius Zaleckas <paulius.zaleckas@teltonika.lt>
> 
> wimax connection manager / daemon has to know what is current
> state of the device. Previously it was only possible to get
> notification whet state has changed.
> 
> Signed-off-by: Paulius Zaleckas <paulius.zaleckas@teltonika.lt>
> ---
>  include/linux/wimax.h    |    5 +++
>  net/wimax/Makefile       |    1 +
>  net/wimax/debug-levels.h |    1 +
>  net/wimax/debugfs.c      |    1 +
>  net/wimax/op-state-get.c |   86 ++++++++++++++++++++++++++++++++++++++++++++++
>  net/wimax/stack.c        |    5 ++-
>  6 files changed, 98 insertions(+), 1 deletions(-)
>  create mode 100644 net/wimax/op-state-get.c
> 
> diff --git a/include/linux/wimax.h b/include/linux/wimax.h
> index c89de7f..c750f42 100644
> --- a/include/linux/wimax.h
> +++ b/include/linux/wimax.h
> @@ -77,6 +77,7 @@ enum {
>  	WIMAX_GNL_OP_MSG_TO_USER,	/* Kernel to user message */
>  	WIMAX_GNL_OP_RFKILL,	/* Run wimax_rfkill() */
>  	WIMAX_GNL_OP_RESET,	/* Run wimax_rfkill() */
> +	WIMAX_GNL_OP_STATE_GET,		/* Request for current state */
>  	WIMAX_GNL_RE_STATE_CHANGE,	/* Report: status change */
>  };

Won't adding new element in middle of list break existing ABI?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html