Linux-Next discussions
 help / color / mirror / Atom feed
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 15:54:20 +0200	[thread overview]
Message-ID: <1375797260.8219.21.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CA+icZUX8OcTSOABO6Nbz5R6_5-m39rsYOpDqYBA7hf8LFvJLLA@mail.gmail.com> (sfid-20130806_155146_826369_E50BB27F)

On Tue, 2013-08-06 at 15:51 +0200, Sedat Dilek wrote:
> OK, I did not try with debugging enabled and/or w/o Network-Manager.
> 
> If you know of an issue, please let me know.

No, but the dmesg looks like security problems - check wpa_supplicant
log

johannes

  reply	other threads:[~2013-08-06 13:54 UTC|newest]

Thread overview: 15+ 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 [this message]
2013-08-06 14:02   ` Sedat Dilek
2013-08-06 14:46   ` Sedat Dilek
2013-08-06 14:50     ` Johannes Berg
2013-08-06 14:56       ` Sedat Dilek
2013-08-06 14:57         ` Johannes Berg
     [not found]           ` <1375801059.8219.24.camel-8Nb76shvtaUJvtFkdXX2HixXY32XiHfO@public.gmane.org>
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

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=1375797260.8219.21.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