All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: sedat.dilek@gmail.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: linux-next: Tree for Aug 6 [ wireless | iwlwifi | mac80211 ? ]
Date: Tue, 06 Aug 2013 18:03:18 +0200	[thread overview]
Message-ID: <1375804998.8219.27.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CA+icZUW7LVzg7sM3O-w5oQpeaj=CT6MS6Q7cRZ1qK0h-Z4wZuw@mail.gmail.com> (sfid-20130806_175826_831897_11A1C276)

[reducing mailing lists - Stephen if you want off let us know]

On Tue, 2013-08-06 at 17:58 +0200, Sedat Dilek wrote:

> $ cat /proc/version
> Linux version 3.11.0-rc4-1-wl-20130805 (sedat.dilek@gmail.com@fambox)
> (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #1 SMP Tue Aug 6
> 17:52:45 CEST 2013
> 
> This kernel boots fine and has no WiFi problems.
> 
> > You assume a breakage in a different area than wireless or network in general?
> >
> 
> Any wild guess?

Not really, but maybe you can pull the other trees on top again and see
if those broke it? I don't really think/hope so but it's possible that
one of my pending pull requests broke it, I guess?

johannes


  reply	other threads:[~2013-08-06 16:03 UTC|newest]

Thread overview: 39+ 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:51 ` 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
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 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 [this message]
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 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 21:56                                                         ` Hannes Frederic Sowa
2013-08-06 22:55                                                         ` Sedat Dilek
2013-08-06 23:07                                                           ` Hannes Frederic Sowa
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=1375804998.8219.27.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --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 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.