From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: kernel oops on wireless-testing
Date: Tue, 10 Jul 2012 13:09:20 +0200 [thread overview]
Message-ID: <1341918560.4475.10.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4FFC0BA2.3060107@broadcom.com> (sfid-20120710_130212_744547_93D9E56B)
On Tue, 2012-07-10 at 13:01 +0200, Arend van Spriel wrote:
> Recently I get a kernel oops in nightly test on the wireless-testing
> tree (see below). This is on 3.5-rc4 kernel based on following commit:
>
> commit a5b846deb890fbea72267e4e7d98f8f022959d14
> Merge: 1532e30 bf52592
> Author: John W. Linville <linville@tuxdriver.com>
> Date: Wed Jun 27 16:15:29 2012 -0400
>
> Merge branch 'master' of
> git://git.kernel.org/pub/scm/linux/kernel/git/linvi
>
> Can this be expected (eg. recent change in struct wiphy) ? I will built
> a new kernel from wireless-testing and see if that helps.
Why would you expect this? Are you running new modules on an old kernel?
johannes
next prev parent reply other threads:[~2012-07-10 11:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 11:01 kernel oops on wireless-testing Arend van Spriel
2012-07-10 11:09 ` Johannes Berg [this message]
2012-07-10 12:38 ` Arend van Spriel
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=1341918560.4475.10.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).