From: Johannes Berg <johannes@sipsolutions.net>
To: Daniel Lublin <quite@hack.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: values in /proc/net/wireless are static, doesn't change; iwlwifi, Intel 6205
Date: Thu, 11 Jun 2015 10:39:42 +0200 [thread overview]
Message-ID: <1434011982.1915.4.camel@sipsolutions.net> (raw)
In-Reply-To: <loom.20150611T103011-578@post.gmane.org> (sfid-20150611_103051_260554_CB70491A)
On Thu, 2015-06-11 at 08:30 +0000, Daniel Lublin wrote:
> > The fix just went into net.git.
>
> Aha! There you go. Where do I find it? Beginner kernel git diver...
https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=9c5a18a31b321f120efda412281bb9f610f84aa0
johannes
prev parent reply other threads:[~2015-06-11 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 7:55 values in /proc/net/wireless are static, doesn't change; iwlwifi, Intel 6205 Daniel Lublin
2015-06-11 8:06 ` Johannes Berg
2015-06-11 8:30 ` Daniel Lublin
2015-06-11 8:39 ` 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=1434011982.1915.4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=quite@hack.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).