From: Richard Purdie <rpurdie@rpsys.net>
To: Dominik Brodowski <linux@dominikbrodowski.net>,
Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Pavel Machek <pavel@ucw.cz>,
linux-pcmcia@lists.infradead.org, lenz@cs.wisc.edu,
kernel list <linux-kernel@vger.kernel.org>,
metan@seznam.cz
Subject: Re: 2.6.17-rc1: collie -- oopsen in pccardd?
Date: Fri, 14 Apr 2006 00:18:34 +0100 [thread overview]
Message-ID: <1144970315.7236.23.camel@localhost.localdomain> (raw)
In-Reply-To: <20060413171425.GA12404@isilmar.linta.de>
On Thu, 2006-04-13 at 19:14 +0200, Dominik Brodowski wrote:
> Oh yes, mea culpa. However, we can simply remove setting res->flags here, as
> we never read it in this case anyways.
>
> Thanks,
> Dominik
>
>
> From: Dominik Brodowski <linux@dominikbrodowski.net>
> Date: Thu Apr 13 19:06:49 2006 +0200
> Subject: [PATCH] pcmcia: fix oops in static mapping case
>
> As static maps do not have IO resources, this setting oopses. However, as
> we do not ever read this value, we can safely remove it.
>
> Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
>
> diff --git a/drivers/pcmcia/pcmcia_resource.c
> b/drivers/pcmcia/pcmcia_resource.c
> index 2539c0b..cc3402c 100644
> --- a/drivers/pcmcia/pcmcia_resource.c
> +++ b/drivers/pcmcia/pcmcia_resource.c
> @@ -88,7 +88,6 @@ static int alloc_io_space(struct pcmcia_
> }
> if ((s->features & SS_CAP_STATIC_MAP) && s->io_offset) {
> *base = s->io_offset | (*base & 0x0fff);
> - s->io[0].res->flags = (s->io[0].res->flags &
> ~IORESOURCE_BITS) | (attr & IORESOURCE_BITS);
> return 0;
> }
> /* Check for an already-allocated window that must conflict
I can confirm this fixes the problem I was seeing as well.
Thanks,
Richard
prev parent reply other threads:[~2006-04-13 23:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 12:22 2.6.17-rc1: collie -- oopsen in pccardd? Pavel Machek
2006-04-04 12:43 ` Russell King
2006-04-04 0:01 ` Pavel Machek
2006-04-13 10:11 ` Richard Purdie
2006-04-13 16:47 ` Pavel Machek
2006-04-13 16:54 ` Russell King
2006-04-13 17:14 ` Dominik Brodowski
2006-04-13 19:19 ` Pavel Machek
2006-04-13 23:18 ` Richard Purdie [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=1144970315.7236.23.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux@dominikbrodowski.net \
--cc=metan@seznam.cz \
--cc=pavel@ucw.cz \
--cc=rmk+lkml@arm.linux.org.uk \
/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