From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>
Cc: linux-ide@vger.kernel.org
Subject: Re: PATCH: Add fixup functionality to the PCI drivers
Date: Fri, 05 Nov 2004 23:29:09 +0000 [thread overview]
Message-ID: <1099697347.5630.78.camel@localhost.localdomain> (raw)
In-Reply-To: <200411052313.06968.bzolnier@elka.pw.edu.pl>
On Gwe, 2004-11-05 at 22:13, Bartlomiej Zolnierkiewicz wrote:
> > + * Perform the generic probe and if it is successful invoke any
> > + * remaining post probe fixup logic in the driver itself.
> > + */
> > +static void probe_pci_hwif_init(ide_hwif_t *hwif, ide_pci_device_t *d) {
> > + probe_hwif_init_with_fixup(hwif, d->fixup);
> > +}
>
> this wrapper is not needed
True
> > @@ -749,13 +761,13 @@
> > ata_index_t index_list2 = do_ide_setup_pci_device(dev2, d, 0);
> >
> > if ((index_list.b.low & 0xf0) != 0xf0)
> > - probe_hwif_init(&ide_hwifs[index_list.b.low]);
> > + probe_pci_hwif_init(&ide_hwifs[index_list.b.low], d);
> > if ((index_list.b.high & 0xf0) != 0xf0)
> > - probe_hwif_init(&ide_hwifs[index_list.b.high]);
> > + probe_pci_hwif_init(&ide_hwifs[index_list.b.high], d);
> > if ((index_list2.b.low & 0xf0) != 0xf0)
> > - probe_hwif_init(&ide_hwifs[index_list2.b.low]);
> > + probe_pci_hwif_init(&ide_hwifs[index_list2.b.low], d);
> > if ((index_list2.b.high & 0xf0) != 0xf0)
> > - probe_hwif_init(&ide_hwifs[index_list2.b.high]);
> > + probe_pci_hwif_init(&ide_hwifs[index_list2.b.high], d);
> >
> > create_proc_ide_interfaces();
> > }
>
> this chunk is not needed
Disagree. Look more carefully - we always need to pass d so we can pass
d->fixup
next prev parent reply other threads:[~2004-11-06 0:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 16:40 PATCH: Add fixup functionality to the PCI drivers Alan Cox
2004-11-05 22:13 ` Bartlomiej Zolnierkiewicz
2004-11-05 23:29 ` Alan Cox [this message]
2004-11-06 0:44 ` Bartlomiej Zolnierkiewicz
2004-11-05 23:43 ` Alan Cox
2004-11-06 16:05 ` 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=1099697347.5630.78.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@elka.pw.edu.pl \
--cc=linux-ide@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.