From: Jeremy Higdon <jeremy@sgi.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: gwh@sgi.com, jbarnes@sgi.com, aniket_m@hotmail.com,
linux-kernel@vger.kernel.org
Subject: Re: Patch to add support for SGI's IOC4 chipset
Date: Mon, 20 Oct 2003 23:35:36 -0700 [thread overview]
Message-ID: <20031021063536.GA78855@sgi.com> (raw)
In-Reply-To: <200310162020.51303.bzolnier@elka.pw.edu.pl>
On Thu, Oct 16, 2003 at 08:20:51PM +0200, Bartlomiej Zolnierkiewicz wrote:
>
> > I will be on a vacation starting tomorrow, so I won't be able to reply
> > until Oct 19th or 20th, in case there are any more issues. Hopefully this
> > one will be okay :-)
>
> I think that after applying attached incremental patch it can go in.
Thanks. I'll test this and reply with the results.
> - defining IDE_ARCH_ACK_INTR and ide_ack_intr() in sgiioc4.c is a no-op,
> it should be done <asm/ide.h> to make it work
> (I think the same problem is present in 2.4.x)
The definition in <include/linux/ide.h> is only used if IDE_ARCH_ACK_INTR is
not defined. sgiioc4.c defines IDE_ARCH_ACK_INTR before including that file,
so I believe we get the definition we want without touching ide.h, don't we?
> - fix NULL pointer dereference (accessing hwif->name while hwif is NULL)
> in sgiioc4_ide_setup_pci_device() (was this driver ever tested?)
Yes. It may be that since name is an array, the value passed to request_region
was the offset of name in the structure. Since that was never dereferenced,
things worked okay. In any case, the code was obviously incorrect.
> - make config option SN2 specific
> - replace uint{8,32,64}_t by u{8,32,64}
These look fine.
I'll await a response on the IDE_ARCH_ACK_INTR issue. Do you want me to send
another patch, or is the previous with your update sufficient?
thanks
jeremy
next prev parent reply other threads:[~2003-10-21 6:36 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
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 [this message]
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=20031021063536.GA78855@sgi.com \
--to=jeremy@sgi.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=aniket_m@hotmail.com \
--cc=gwh@sgi.com \
--cc=jbarnes@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