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:18:35 +0200 [thread overview]
Message-ID: <1375816715.8219.29.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CA+icZUXaTYVc_iv3hny6Je9mVdX8KCVpFSNBeukS+Fh-347Wvw@mail.gmail.com> (sfid-20130806_211440_311168_A2CCF549)
On Tue, 2013-08-06 at 21:14 +0200, Sedat Dilek wrote:
> On Tue, Aug 6, 2013 at 9:08 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
> > 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.
> >
>
> git-bisecting... 2 steps to go...
>
> This one is bad... "af_packet: simplify VLAN frame check in packet_snd"
>
> http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=c483e02614551e44ced3fe6eedda8e36d3277ccc
That seems weird, does reverting it fix it?
johannes
next prev parent reply other threads:[~2013-08-06 19:18 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
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 [this message]
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=1375816715.8219.29.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 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.