Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: sedat.dilek@gmail.com
Cc: David Miller <davem@davemloft.net>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	wireless <linux-wireless@vger.kernel.org>,
	netdev@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 6 [ wireless | iwlwifi | mac80211 ? ]
Date: Tue, 06 Aug 2013 21:08:48 +0200	[thread overview]
Message-ID: <1375816128.8219.28.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CA+icZUXpZaHu-FjR6FGnbkG0XEkiukEgYYbDmrSjdqNz4rWCNg@mail.gmail.com> (sfid-20130806_203509_940812_0A82B457)

On Tue, 2013-08-06 at 20:35 +0200, Sedat Dilek wrote:

> Attached is a diff comparing all new commits in next-20130805.
> If one of the commits smells bad to you, please let me know.

Out of that list, only the af_packet changes would seem to have any
impact on wireless at all.

johannes


  reply	other threads:[~2013-08-06 19:08 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
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 [this message]
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=1375816128.8219.28.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=davem@davemloft.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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