From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
Emmanuel Grumbach <egrumbach@gmail.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: wireless_nlevent_flush backported to stable kernels
Date: Tue, 17 May 2016 11:08:56 +0200 [thread overview]
Message-ID: <1463476136.2265.0.camel@sipsolutions.net> (raw)
In-Reply-To: <573ADEF3.8030408@broadcom.com> (sfid-20160517_110608_933524_91834CD9)
On Tue, 2016-05-17 at 11:05 +0200, Arend Van Spriel wrote:
>
> I remember and so the suggestion was to maintain a list of functions
> to check. Or did you pursue that as well with same result?
Well I had it set up that way, compiling a little test thing for each
function. Each one took quite a while, I don't remember the data
though.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
prev parent reply other threads:[~2016-05-17 9:09 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
2016-05-16 19:26 ` Johannes Berg
2016-05-17 9:05 ` Arend Van Spriel
2016-05-17 9:08 ` Johannes Berg [this message]
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=1463476136.2265.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=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.