From: Andrew Morton <akpm@osdl.org>
To: Aniket Malatpure <aniket@sgi.com>
Cc: linux-kernel@vger.kernel.org, gwh@sgi.com, jeremy@sgi.com,
jbarnes@sgi.com, aniket_m@hotmail.com,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: Re: Patch to add support for SGI's IOC4 chipset
Date: Thu, 2 Oct 2003 17:43:04 -0700 [thread overview]
Message-ID: <20031002174304.5c984dc9.akpm@osdl.org> (raw)
In-Reply-To: <3F7CB4A9.3C1F1237@sgi.com>
Aniket Malatpure <aniket@sgi.com> wrote:
>
> Hi
>
> This patch adds support for the ATAPI part of SGI's IOC4 chipset.
> A version of this patch for the 2.4 series has been accepted and is present in the tree.
> This patch is a slight modification of the earlier patch for the 2.4 series.
>
Perhaps Bart could take a look over this sometime please?
> +++ b/drivers/ide/pci/sgiioc4.c Thu Oct 2 16:53:34 2003
> +
> +extern int dma_timer_expiry(ide_drive_t * drive);
This is unused. Just as well, as it is static to a different file.
> +static struct pci_device_id sgiioc4_pci_tbl[] __devinitdata = {
This cannot be __devinitdata because the PCI table walking will look at it
even after __init code has been dropped. We've had oopses from this.
> --- /dev/null Wed Dec 31 16:00:00 1969
> +++ b/drivers/ide/pci/sgiioc4.h Thu Oct 2 16:53:34 2003
hrm, why does this file exist? It has only one include site, and should
not be included by other .c files anyway because it defines static storage.
It looks like the whole file should just be pasted into sgiioc4.c?
> +typedef volatile struct {
> + u32 timing_reg0;
> + u32 timing_reg1;
> + u32 low_mem_ptr;
> + u32 high_mem_ptr;
> + u32 low_mem_addr;
> + u32 high_mem_addr;
> + u32 dev_byte_count;
> + u32 mem_byte_count;
> + u32 status;
> +} ioc4_dma_regs_t;
Does this actually need to be volatile?
next prev parent reply other threads:[~2003-10-03 0:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 23:28 Aniket Malatpure
2003-10-03 0:43 ` Andrew Morton [this message]
2003-10-03 14:45 ` Bartlomiej Zolnierkiewicz
2003-10-03 14:55 ` Jeff Garzik
2003-10-03 15:13 ` Bartlomiej Zolnierkiewicz
2003-10-04 1:52 ` Aniket Malatpure
2003-10-04 0:32 ` Aniket Malatpure
2003-10-04 17:30 ` Bartlomiej Zolnierkiewicz
2003-10-07 8:27 ` Jeremy Higdon
2003-10-07 13:27 ` Bartlomiej Zolnierkiewicz
2003-10-08 3:38 ` Jeremy Higdon
2003-10-16 18:20 ` Bartlomiej Zolnierkiewicz
2003-10-21 6:35 ` Jeremy Higdon
2003-10-21 14:39 ` Bartlomiej Zolnierkiewicz
2003-10-22 4:30 ` Jeremy Higdon
2003-10-22 18:31 ` Bartlomiej Zolnierkiewicz
2003-10-23 4:34 ` Jeremy Higdon
2003-10-25 2:09 ` Jeremy Higdon
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=20031002174304.5c984dc9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=aniket@sgi.com \
--cc=aniket_m@hotmail.com \
--cc=gwh@sgi.com \
--cc=jbarnes@sgi.com \
--cc=jeremy@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome