From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: wireless_nlevent_flush backported to stable kernels
Date: Sun, 15 May 2016 11:50:54 +0200 [thread overview]
Message-ID: <5738467E.4020005@broadcom.com> (raw)
In-Reply-To: <CANUX_P1i8MYwsbcnvjbqrHZ77aMOZHZ6ug3VzHvn=3pUU_czyw@mail.gmail.com>
On 15-5-2016 8:25, Emmanuel Grumbach wrote:
> Hi,
>
> Johanne's patch:
>
> commit cb150b9d23be6ee7f3a0fff29784f1c5b5ac514d
> Author: Johannes Berg <johannes.berg@intel.com>
> Date: Wed Jan 27 13:29:34 2016 +0100
>
> cfg80211/wext: fix message ordering
>
>
> has been backported to more stable kernels and hence backport needs to
> take that into account.
> I am using Ubuntu's wily kernel (4.2 based) and apparently, they
> backported Johanne's fix as well.
>
> On my system, I fixed it with the patch below, but it is surely not good enough.
In general this is avoided by preceeding the stub function with:
#define wireless_nlevent_flush LINUX_BACKPORT(wireless_nlevent_flush)
This way you will use the stub and not the in-kernel function. There has
been discussions about adding a mechanism to avoid backport if kernel
has the function available. No actual work in that area has been done yet.
Regards,
Arend
> diff --git a/backport-include/net/iw_handler.h
> b/backport-include/net/iw_handler.h
> index e205d1e..b9c0144 100644
> --- a/backport-include/net/iw_handler.h
> +++ b/backport-include/net/iw_handler.h
> @@ -25,7 +25,8 @@ iwe_stream_add_point_check(struct iw_request_info
> *info, char *stream,
> return res;
> }
> #endif /* LINUX_VERSION_CODE < KERNEL_VERSION(4,1,0) */
> -#if LINUX_VERSION_CODE < KERNEL_VERSION(4,4,6)
> +#if LINUX_VERSION_CODE < KERNEL_VERSION(4,4,6) && \
> + LINUX_VERSION_CODE < KERNEL_VERSION(4,1,21)
> static inline void wireless_nlevent_flush(void) {}
> #endif
> #endif /* __BACKPORT_IW_HANDLER_H */
>
>
> Emmanuel Grumbach
> egrumbach@gmail.com
> --
> To unsubscribe from this list: send the line "unsubscribe backports" in
>
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2016-05-15 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-15 6:25 wireless_nlevent_flush backported to stable kernels Emmanuel Grumbach
2016-05-15 9:50 ` Arend Van Spriel [this message]
2016-05-16 19:26 ` Johannes Berg
2016-05-17 9:05 ` Arend Van Spriel
2016-05-17 9:08 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5738467E.4020005@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=egrumbach@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.