From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH 2/2] ide: pass hw_regs_t-s to ide_device_add[_all]()
Date: Sun, 22 Jun 2008 10:58:46 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0806221055210.4607@anakin> (raw)
In-Reply-To: <200806202029.11304.bzolnier@gmail.com>
On Fri, 20 Jun 2008, Bartlomiej Zolnierkiewicz wrote:
> * Add 'hw_regs_t **hws' argument to ide_device_add[_all]() and convert
> host drivers + drivers/ide/setup-pci.c to use it instead of calling
> ide_init_port_hw() directly (however if host has more than 1 port we
> must still set hwif->chipset to hint consecutive ide_find_port() call
> that the ide_hwifs[] slot is occupied).
>
> * Unexport ide_init_port_hw().
>
> There should be no functional changes caused by this patch.
Brr... seems to complicate the bookkeeping a lot...
I looked at the m68k drivers only:
> --- a/drivers/ide/legacy/buddha.c
> +++ b/drivers/ide/legacy/buddha.c
> @@ -148,7 +148,6 @@ static void __init buddha_setup_ports(hw
>
> static int __init buddha_init(void)
> {
> - hw_regs_t hw;
> ide_hwif_t *hwif;
> int i;
>
> @@ -159,6 +158,7 @@ static int __init buddha_init(void)
>
> while ((z = zorro_find_device(ZORRO_WILDCARD, z))) {
> unsigned long board;
> + hw_regs_t hw[3], *hws[] = { NULL, NULL, NULL, NULL };
^
max(BUDDHA_NUM_HWIFS, CATWEASEL_NUM_HWIFS, XSURF_NUM_HWIFS)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Another magic constant, hws[] always has 4 elements?
> --- a/drivers/ide/legacy/gayle.c
> +++ b/drivers/ide/legacy/gayle.c
> @@ -125,6 +125,7 @@ static void __init gayle_setup_ports(hw_
> static int __init gayle_init(void)
> {
> int a4000, i;
> + hw_regs_t hw[2], *hws[] = { NULL, NULL, NULL, NULL };
^
GAYLE_NUM_HWIFS
> Index: b/drivers/ide/legacy/q40ide.c
> ===================================================================
> --- a/drivers/ide/legacy/q40ide.c
> +++ b/drivers/ide/legacy/q40ide.c
> @@ -112,7 +112,7 @@ static int __init q40ide_init(void)
> {
> int i;
> ide_hwif_t *hwif;
> - const char *name;
> + hw_regs_t hw[2], *hws[] = { NULL, NULL, NULL, NULL };
^
Q40IDE_NUM_HWIFS
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2008-06-22 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 18:29 Bartlomiej Zolnierkiewicz
2008-06-22 8:58 ` Geert Uytterhoeven [this message]
2008-06-22 13:22 ` Bartlomiej Zolnierkiewicz
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=Pine.LNX.4.64.0806221055210.4607@anakin \
--to=geert@linux-m68k.org \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@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
all inboxes | Powered by JetHome®