From: Komuro <komurojun-mbn@nifty.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: linux-pcmcia@lists.infradead.org, alsa-devel@alsa-project.org,
Michael Buesch <mb@bu3sch.de>,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-wireless@vger.kernel.org, laforge@gnumonks.org,
linux-ide@vger.kernel.org, linux-mtd@lists.infradead.org,
Dominik Brodowski <linux@dominikbrodowski.net>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io()
Date: Sun, 8 Aug 2010 22:07:31 +0900 (JST) [thread overview]
Message-ID: <103911.103501281272851252.komurojun-mbn@nifty.com> (raw)
In-Reply-To: <1281046014-7585-11-git-send-email-linux@dominikbrodowski.net>
Hi,
>
>- link->io.IOAddrLines =10;
>- link->io.Attributes1 = IO_DATA_PATH_WIDTH_16;
>+ link->resource[0]->flags |= IO_DATA_PATH_WIDTH_16;
link->io_lines should be set here?
>@@ -840,14 +839,15 @@ xirc2ps_config(struct pcmcia_device * link)
> }
> printk(KNOT_XIRC "no ports available\n");
> } else {
>- link->io.NumPorts1 = 16;
>+ link->io_lines = 10;
>+ link->resource[0]->end = 16;
Best Regards
Komuro
prev parent reply other threads:[~2010-08-08 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100805220511.GA7040@comet.dominikbrodowski.net>
2010-08-05 22:06 ` [PATCH 07/18] pcmcia: use pcmica_{read,write}_config_byte Dominik Brodowski
2010-08-05 22:06 ` [PATCH 10/18] pcmcia: do not use io_req_t after call to pcmcia_request_io() Dominik Brodowski
2010-08-05 22:06 ` [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io() Dominik Brodowski
2010-08-05 22:06 ` [PATCH 13/18] pcmcia: remove memreq_t Dominik Brodowski
2010-08-05 22:06 ` [PATCH 14/18] pcmcia: use struct resource for PCMCIA devices, part 2 Dominik Brodowski
2010-08-05 22:06 ` [PATCH 17/18] pcmcia: do not request windows if you don't need to Dominik Brodowski
2010-08-08 13:07 ` Komuro [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=103911.103501281272851252.komurojun-mbn@nifty.com \
--to=komurojun-mbn@nifty.com \
--cc=alsa-devel@alsa-project.org \
--cc=laforge@gnumonks.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mb@bu3sch.de \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).