From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: linux-kernel@vger.kernel.org
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: Re: Linux 2.6.3-rc1
Date: Mon, 9 Feb 2004 13:41:08 +0100 [thread overview]
Message-ID: <200402091341.08526.arekm@pld-linux.org> (raw)
In-Reply-To: <4026F312.60703@tomt.net>
Dnia Monday 09 of February 2004 03:40, Andre Tomt napisał:
> Ahh, indeed it does, _but_
>
> pdc202xx_old seems to have the same bug, making via82cxxx crash later on
> instead.
>
> Doing the same change to pdc202xx_old.h (removing __initdata) fixes this
> case too :-)
What about others?
./pdc202xx_old.h:static ide_pci_host_proc_t pdc202xx_procs[] = {
./hpt34x.h:static ide_pci_host_proc_t hpt34x_procs[] __initdata = {
./alim15x3.h:static ide_pci_host_proc_t ali_procs[] __initdata = {
./amd74xx.h:static ide_pci_host_proc_t amd74xx_procs[] __initdata = {
./cs5530.h:static ide_pci_host_proc_t cs5530_procs[] __initdata = {
./pdc202xx_new.h:static ide_pci_host_proc_t pdcnew_procs[] = {
./piix.h:static ide_pci_host_proc_t piix_procs[] __devinitdata = {
./sc1200.h:static ide_pci_host_proc_t sc1200_procs[] __initdata = {
./slc90e66.h:static ide_pci_host_proc_t slc90e66_procs[] __initdata = {
./serverworks.h:static ide_pci_host_proc_t svwks_procs[] __initdata = {
./cmd64x.h:static ide_pci_host_proc_t cmd64x_procs[] __initdata = {
./aec62xx.h:static ide_pci_host_proc_t aec62xx_procs[] __initdata = {
./siimage.h:static ide_pci_host_proc_t siimage_procs[] __initdata = {
./sis5513.h:static ide_pci_host_proc_t sis_procs[] __initdata = {
./via82cxxx.h:static ide_pci_host_proc_t via_procs[] __initdata = {
./hpt366.h:static ide_pci_host_proc_t hpt366_procs[] __initdata = {
./triflex.h:static ide_pci_host_proc_t triflex_proc __initdata = {
./cs5520.h:static ide_pci_host_proc_t cs5520_procs[] __initdata = {
all these __initdata (one __devinitdata) should also be removed?
--
Arkadiusz Miśkiewicz CS at FoE, Wroclaw University of Technology
arekm.pld-linux.org, 1024/3DB19BBD, JID: arekm.jabber.org, PLD/Linux
next prev parent reply other threads:[~2004-02-09 12:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 2:28 Linux 2.6.3-rc1 Linus Torvalds
2004-02-07 2:56 ` viro
2004-02-07 17:21 ` Kevin O'Connor
2004-02-07 19:20 ` Greg KH
2004-02-07 3:11 ` Måns Rullgård
2004-02-07 5:26 ` Greg KH
2004-02-07 10:24 ` Andre Tomt
2004-02-07 16:22 ` Bartlomiej Zolnierkiewicz
2004-02-08 6:02 ` Andre Tomt
2004-02-08 6:29 ` Andre Tomt
2004-02-08 21:34 ` Bartlomiej Zolnierkiewicz
2004-02-08 21:55 ` Andre Tomt
2004-02-08 22:51 ` Bartlomiej Zolnierkiewicz
2004-02-09 0:08 ` Andre Tomt
2004-02-09 1:34 ` Bartlomiej Zolnierkiewicz
2004-02-09 2:40 ` Andre Tomt
2004-02-09 12:41 ` Arkadiusz Miskiewicz [this message]
2004-02-09 14:41 ` Bartlomiej Zolnierkiewicz
2004-02-09 13:01 ` Bartlomiej Zolnierkiewicz
2004-02-09 1:53 ` Disassembling with gdb (Re: Linux 2.6.3-rc1) Matthew Reppert
2004-02-08 15:18 ` Linux 2.6.3-rc1 Geert Uytterhoeven
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=200402091341.08526.arekm@pld-linux.org \
--to=arekm@pld-linux.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--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