From: Komuro <komurojun@nifty.com>
To: linux-kernel@vger.kernel.org
Cc: linas@austin.ibm.com
Subject: RE: [PATCH] Simplify yenta code
Date: Sat, 6 Oct 2007 13:26:01 +0900 [thread overview]
Message-ID: <20071006132601.f944f461.komurojun@nifty.com> (raw)
Hello,
Unfortunately, your patch is wrong,
and does not results in the same run-time behaviour.
You broke the code of "if (type & IORESOURCE_IO)"
Best Regards
Komuro
>Simplify some of the resource detection logic in yenta_socket.
>This patch results in the same run-time behaviour as the
>current code, but does so with fewer lines of code. This
>makes the logical flow of the code a bit easier to understand.
>
>Signed-off-by: Linas Vepstas <linas@austin.ibm.com>
>Cc: Dominik Brodowski <linux@brodo.de>
>
>----
> drivers/pcmcia/yenta_socket.c | 22 ++++++++--------------
> 1 file changed, 8 insertions(+), 14 deletions(-)
>
>Index: linux-2.6.23-rc8-mm1/drivers/pcmcia/yenta_socket.c
>===================================================================
>--- linux-2.6.23-rc8-mm1.orig/drivers/pcmcia/yenta_socket.c 2007-10-01 >12:17:02.000000000 -0500
>+++ linux-2.6.23-rc8-mm1/drivers/pcmcia/yenta_socket.c 2007-10-01 12:37:36.000000000 >-0500
>@@ -654,20 +654,14 @@ static int yenta_allocate_res(struct yen
> pci_name(socket->dev), nr);
> }
>
>- if (type & IORESOURCE_IO) {
>- if ((yenta_search_res(socket, res, BRIDGE_IO_MAX)) ||
>- (yenta_search_res(socket, res, BRIDGE_IO_ACC)) ||
>- (yenta_search_res(socket, res, BRIDGE_IO_MIN)))
>- return 1;
>- } else {
>- if (type & IORESOURCE_PREFETCH) {
>- if ((yenta_search_res(socket, res, BRIDGE_MEM_MAX)) ||
>- (yenta_search_res(socket, res, BRIDGE_MEM_ACC)) ||
>- (yenta_search_res(socket, res, BRIDGE_MEM_MIN)))
>- return 1;
>- /* Approximating prefetchable by non-prefetchable */
>- res->flags = IORESOURCE_MEM;
>- }
>+ if ((yenta_search_res(socket, res, BRIDGE_MEM_MAX)) ||
>+ (yenta_search_res(socket, res, BRIDGE_MEM_ACC)) ||
>+ (yenta_search_res(socket, res, BRIDGE_MEM_MIN)))
>+ return 1;
>+
>+ if (type & IORESOURCE_PREFETCH) {
>+ /* Approximating prefetchable by non-prefetchable */
>+ res->flags = IORESOURCE_MEM;
> if ((yenta_search_res(socket, res, BRIDGE_MEM_MAX)) ||
> (yenta_search_res(socket, res, BRIDGE_MEM_ACC)) ||
> (yenta_search_res(socket, res, BRIDGE_MEM_MIN)))
>-
next reply other threads:[~2007-10-06 4:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 4:26 Komuro [this message]
2007-10-08 17:47 ` [PATCH] Simplify yenta code Linas Vepstas
2007-10-13 22:36 ` [NOT VERY SAFE] [TCP]: Set initial_ssthresh default to zero in Cubic and BIC Komuro
2007-10-13 22:52 ` David Miller
2007-10-13 22:54 ` David Miller
2007-10-14 1:02 ` Komuro
2007-10-14 2:38 ` David Miller
2007-10-14 4:30 ` Jeff Garzik
2007-10-14 4:28 ` Komuro
2007-10-14 4:32 ` David Miller
2007-10-14 4:53 ` Komuro
2007-10-14 5:23 ` David Miller
2007-10-15 12:59 ` Komuro
2007-10-15 15:55 ` Stephen Hemminger
2007-10-14 20:34 ` Stephen Hemminger
2008-03-02 12:07 ` [BUG kernel 2.6.25-rc3 IPV6] ping6 -I eth0 ff02::1 causes system hang Komuro
2008-03-02 12:27 ` YOSHIFUJI Hideaki / 吉藤英明
2008-03-03 22:06 ` Komuro
2008-03-04 17:49 ` Brian Haley
2008-03-04 7:40 ` Andrew Morton
2008-03-08 4:44 ` Komuro
2008-03-08 5:20 ` Komuro
2008-03-08 11:56 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2007-10-01 18:41 [PATCH] Simplify yenta code Linas Vepstas
2007-10-01 18:56 ` Matthew Wilcox
2007-10-01 20:04 ` Linas Vepstas
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=20071006132601.f944f461.komurojun@nifty.com \
--to=komurojun@nifty.com \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@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.