linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Rob Hussey <robjhussey@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Kernel panic with rt2500pci built-in
Date: Fri, 07 Sep 2007 21:37:20 +0200	[thread overview]
Message-ID: <1189193840.28781.197.camel@johannes.berg> (raw)
In-Reply-To: <6b8cef970709071231s5693b835vaf8493254c8292da@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 955 bytes --]

On Fri, 2007-09-07 at 15:31 -0400, Rob Hussey wrote:

> This was with wireless-dev git. I can try DEBUG_KOBJECT once I get a chance.

That'd be good.

> I'd like to try to bisect this though, but I'm having trouble finding
> a point in which it worked.

> If I do:
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git
> and then:
> git pull . remotes/origin/rt2x00
> 
> Then my commit history has all rt2x00 commits on top, and trying to
> reset to an earlier point in time reverts rt2x00 commits, but not
> wireless-dev commits (unless I  reset to before the initial rt2x00
> commit). This causes compile errors mostly involving undeclared stuff
> prefixed "IEEE80211_" Is there a better way to do this? Did I even
> start out correctly?

I'm not sure you can bisect due to the way mac80211/rt2x00 are currently
developed, in lockstep but in different branches that are pulled
together.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2007-09-07 19:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06  3:06 Kernel panic with rt2500pci built-in Rob Hussey
2007-09-06  3:25 ` Rob Hussey
2007-09-06  3:53   ` Rob Hussey
2007-09-06 12:12   ` Johannes Berg
2007-09-07  0:45   ` Johannes Berg
2007-09-07 19:31     ` Rob Hussey
2007-09-07 19:37       ` Johannes Berg [this message]
2007-09-07 21:38         ` Rob Hussey
2007-09-07 22:00           ` Johannes Berg
2007-09-08  4:29             ` Rob Hussey
2007-09-08  4:40               ` Rob Hussey
2007-09-08  7:49                 ` Johannes Berg
2007-09-08  8:26                   ` Rob Hussey
2007-09-08  9:36                     ` Johannes Berg
2007-09-08 15:57                       ` Rob Hussey
2007-09-08 16:16                         ` Ivo van Doorn
2007-09-08 16:39                           ` Rob Hussey
2007-09-08 17:18                             ` Ivo van Doorn
2007-09-08 17:16                               ` Rob Hussey
2007-09-08 17:39                                 ` Ivo van Doorn
2007-09-08 18:28                                   ` Rob Hussey
2007-09-10 10:31                             ` Johannes Berg
2007-09-10 11:05                               ` Johannes Berg
2007-09-10 20:40                                 ` Rob Hussey
2007-09-10 21:25                                   ` Rob Hussey
2007-09-11 10:17                                     ` Johannes Berg

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=1189193840.28781.197.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=robjhussey@gmail.com \
    /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).