From: Johannes Berg <johannes@sipsolutions.net>
To: sedat.dilek@gmail.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: linux-next: Tree for Aug 6 [ wireless | iwlwifi | mac80211 ? ]
Date: Tue, 06 Aug 2013 16:50:17 +0200 [thread overview]
Message-ID: <1375800617.8219.23.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CA+icZUUAJ25QybqHvxz7eubSLH6YuNjcc5zyU2O5Xi9vevMGkw@mail.gmail.com> (sfid-20130806_164606_692527_0D2AF4DB)
On Tue, 2013-08-06 at 16:46 +0200, Sedat Dilek wrote:
Heh, the interesting messages are always cut out of the log:
Aug 6 16:30:34 fambox wpa_supplicant[2533]: wlan0: WPA: RX message 1 of 4-Way Handshake from 00:04:0e:e4:00:3d (ver=2)
Aug 6 16:30:34 fambox wpa_supplicant[2533]: RSN: msg 1/4 key data - hexdump(len=0):
Aug 6 16:30:34 fambox wpa_supplicant[2533]: Get randomness: len=32 entropy=4
Aug 6 16:30:34 fambox wpa_supplicant[2533]: random from os_get_random - hexdump(len=32): [REMOVED]
Aug 6 16:30:34 fambox wpa_supplicant[2533]: random_mix_pool - hexdump(len=20): [REMOVED]
Aug 6 16:30:34 fambox wpa_supplicant[2533]: random from internal pool - hexdump(len=16): [REMOVED]
Aug 6 16:30:34 fambox wpa_supplicant[2533]: random_mix_pool - hexdump(len=20): [REMOVED]
Aug 6 16:30:34 fambox rsyslogd-2177: imuxsock begins to drop messages from pid 2533 due to rate-limiting
[...]
johannes
next prev parent reply other threads:[~2013-08-06 14:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 13:51 linux-next: Tree for Aug 6 [ wireless | iwlwifi | mac80211 ? ] Sedat Dilek
2013-08-06 13:54 ` Johannes Berg
2013-08-06 14:02 ` Sedat Dilek
2013-08-06 14:46 ` Sedat Dilek
2013-08-06 14:50 ` Johannes Berg [this message]
2013-08-06 14:56 ` Sedat Dilek
2013-08-06 14:57 ` Johannes Berg
2013-08-06 14:59 ` Sedat Dilek
2013-08-06 15:09 ` Sedat Dilek
2013-08-06 15:18 ` Johannes Berg
2013-08-06 15:20 ` Sedat Dilek
2013-08-06 15:27 ` Sedat Dilek
2013-08-06 15:29 ` Johannes Berg
2013-08-06 15:43 ` Sedat Dilek
2013-08-06 15:58 ` Sedat Dilek
2013-08-06 16:03 ` Johannes Berg
2013-08-06 16:07 ` Sedat Dilek
2013-08-06 16:51 ` Sedat Dilek
2013-08-06 18:26 ` Sedat Dilek
2013-08-06 18:35 ` Sedat Dilek
2013-08-06 19:08 ` Johannes Berg
2013-08-06 19:14 ` Sedat Dilek
2013-08-06 19:18 ` Johannes Berg
2013-08-06 19:32 ` Sedat Dilek
2013-08-06 19:47 ` Sedat Dilek
2013-08-06 21:29 ` Phil Sutter
2013-08-06 21:40 ` Sedat Dilek
2013-08-06 21:45 ` Johannes Berg
2013-08-06 21:56 ` Hannes Frederic Sowa
2013-08-06 22:55 ` Sedat Dilek
2013-08-06 23:07 ` Hannes Frederic Sowa
2013-08-06 23:14 ` Sedat Dilek
2013-08-06 21:58 ` Johannes Berg
2013-08-08 21:13 ` Phil Sutter
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=1375800617.8219.23.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/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