mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Paul Mackerras <paulus@samba.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Obvious bugfix for yenta resource allocation
Date: Tue, 2 Aug 2005 14:03:43 +0200	[thread overview]
Message-ID: <20050802120343.GA27763@isilmar.linta.de> (raw)
In-Reply-To: <17135.24136.268138.511779@cargo.ozlabs.ibm.com>

On Tue, Aug 02, 2005 at 09:51:36PM +1000, Paul Mackerras wrote:
> Recent changes (well, dating from 12 July) have broken cardbus on my
> powerbook: I get 3 messages saying "no resource of type xxx available,
> trying to continue", and if I plug in my wireless card, it complains
> that there are no resources allocated to the card.  This all worked in
> 2.6.12.
> 
> Looking at the code in yenta_socket.c, function yenta_allocate_res,
> it's obvious what is wrong: if we get to line 639 (i.e. there wasn't a
> usable preassigned resource), we will always flow through to line 668,
> which is the printk that I was seeing, even if a resource was
> successfully allocated.  It looks to me as though there should be a
> return statement after the two config_writel's in each of the 3
> branches of the if statements, so that the function returns after
> successfully setting up the resource.
> 
> The patch below adds these return statements, and with this patch,
> cardbus works on my powerbook once again.
> 
> Signed-off-by: Paul Mackerras <paulus@samba.org>
Acked-by: Dominik Brodowski <linux@dominikbrodowski.net>

Sorry for the bug.

	Dominik

      reply	other threads:[~2005-08-02 12:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02 11:51 Paul Mackerras
2005-08-02 12:03 ` Dominik Brodowski [this message]

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=20050802120343.GA27763@isilmar.linta.de \
    --to=linux@dominikbrodowski.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®