All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Frank Seidel <fseidel@suse.de>
Cc: linux-wireless@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>,
	yi.zhu@intel.com, reinette.chatre@intel.com,
	ipw2100-devel@lists.sourceforge.net
Subject: Re: Problem with Kernel Oops in ipw2200
Date: Wed, 12 Nov 2008 16:33:50 -0500	[thread overview]
Message-ID: <20081112213350.GJ2411@tuxdriver.com> (raw)
In-Reply-To: <49131173.3010409@suse.de>

On Thu, Nov 06, 2008 at 04:46:59PM +0100, Frank Seidel wrote:
> Frank Seidel schrieb:
> > Ever suggestion is very appreciated.
> 
> My first search through the ipw2200 logs pointed
> me to Davids last commit (521c4d96e0840ecce25b956e00f416ed499ef2ba)
> and really after reverting it the problem disappeared here.
> The patch from my last post was the smallest subset of
> the revertion that still works for me here.
> Any comments?

I think it would be better to make sure that ipw2200 (and/or
ieee80211) is properly using netif_carrier_{on,off}() instead?

Thanks,

John
-- 
John W. Linville		Linux should be at the core
linville@tuxdriver.com			of your literate lifestyle.

  reply	other threads:[~2008-11-12 21:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06 15:34 Problem with Kernel Oops in ipw2200 Frank Seidel
2008-11-06 15:46 ` Frank Seidel
2008-11-12 21:33   ` John W. Linville [this message]
2008-11-13  9:16     ` Frank Seidel
2008-11-13 16:03       ` John W. Linville
2008-11-14  2:58       ` Zhu Yi
2008-11-14 10:07         ` Frank Seidel
2008-11-14 14:45         ` Frank Seidel
2008-11-17 10:48         ` [PATCH] " Frank Seidel
2008-11-18 19:23           ` John W. Linville
2008-11-18 19:34             ` reinette chatre
2008-11-21 19:39           ` reinette chatre
2008-11-24 12:44             ` Frank Seidel

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=20081112213350.GJ2411@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=davem@davemloft.net \
    --cc=fseidel@suse.de \
    --cc=ipw2100-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=yi.zhu@intel.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 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.