All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: Chr <chunkeey@web.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-wireless@vger.kernel.org, bugme-daemon@bugzilla.kernel.org
Subject: Re: [RFT/RFC][PATCH] p54: fix misbehavings when firmware can't be found
Date: Wed, 22 Oct 2008 08:05:57 +0000	[thread overview]
Message-ID: <20081022080557.GA38534@atlantis.8hz.com> (raw)
In-Reply-To: <200810212156.24772.chunkeey@web.de>

On Tue, Oct 21, 2008 at 09:56:24PM +0200, Chr wrote:
> On Tuesday 21 October 2008 20:23:13 Andrew Morton wrote:
> > (switched to email.  Please respond via emailed reply-to-all, not via the
> > bugzilla web interface).
> >
> > On Sat, 18 Oct 2008 09:13:00 -0700 (PDT)
> >
> > bugme-daemon@bugzilla.kernel.org wrote:
> > > http://bugzilla.kernel.org/show_bug.cgi?id=11782
> > >
> > >            Summary: p54 misbehaves when firmware can't be found
> > >            Product: Drivers
> > >            Version: 2.5
> > >      KernelVersion: 2.6.27-git8
> > >           Platform: All
> > >         OS/Version: Linux
> > >               Tree: Mainline
> > >             Status: NEW
> > >           Severity: low
> > >           Priority: P1
> > >          Component: network-wireless
> > >         AssignedTo: drivers_network-wireless@kernel-bugs.osdl.org
> > >         ReportedBy: sean@mess.org
> > >
> > >
> > > Latest working kernel version: 2.6.26
> >
> well, you can increase 26 to 27. The patch that caused this regression 
> went into in 2.6.27-gitX so no stable kernel is affected only this pre-rc1...
> 
> anyway, I don't have any p54p hardware right now (for the next two weeks
> to be more precise), so sean you have to test it and report back, otherwise
> this will properly stay RFT...
> 
> I made two versions of the patch, both do the same,
> so it more a matter of which one you would like to have.
> 
> I prefer the first and bigger one, since it hopefully won't break the other 
> patches I send some time ago for wireless-testing...

Both patches work. I tested both patches with the firmware not in place 
(no stack trace) and in place (works as expected).

Thanks
Sean

  reply	other threads:[~2008-10-22  8:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11782-10286@http.bugzilla.kernel.org/>
2008-10-21 18:23 ` [Bugme-new] [Bug 11782] New: p54 misbehaves when firmware can't be found Andrew Morton
2008-10-21 19:56   ` [RFT/RFC][PATCH] p54: fix misbehavings " Chr
2008-10-22  8:05     ` Sean Young [this message]
2008-10-22 12:16       ` [PATCH] " Christian Lamparter
2008-10-22 12:19       ` Chr

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=20081022080557.GA38534@atlantis.8hz.com \
    --to=sean@mess.org \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=chunkeey@web.de \
    --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 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.