From: Ian Soboroff <ian.soboroff@nist.gov>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Muli Ben-Yehuda <mulix@actcom.co.il>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Boot problem, 2.4.19-rc3-ac1
Date: 24 Jul 2002 10:57:14 -0400 [thread overview]
Message-ID: <9cffzy95g39.fsf@rogue.ncsl.nist.gov> (raw)
In-Reply-To: <Pine.LNX.4.44.0207241655011.17209-100000@linux-box.realnet.co.sz>
Zwane Mwaikambo <zwane@linuxpower.ca> writes:
> On 24 Jul 2002, Ian Soboroff wrote:
>
> > static int trident_suspend(struct pci_dev *dev, u32 unused)
> > {
> > - struct trident_card *card = (struct trident_card *) dev;
> > + struct trident_card *card = pci_get_drvdata(dev);
> >
> > if(card->pci_id == PCI_DEVICE_ID_ALI_5451) {
> > ali_save_regs(card);
> > @@ -3466,7 +3466,7 @@
> >
> > static int trident_resume(struct pci_dev *dev)
> > {
> > - struct trident_card *card = (struct trident_card *) dev;
> > + struct trident_card *card = pci_get_drvdata(dev);
> >
> > if(card->pci_id == PCI_DEVICE_ID_ALI_5451) {
> > ali_restore_regs(card);
>
> Thats definitely correct, has this patch been sent to lkml before?
I didn't see it in a quick search at the uwsg.ia.edu archive. The
last ALi patch I see on 2.4 seems to come from Matt Wu at ALi on
4/4/2001.
Anyone have a clue on the IDE part of my question? ;-)
ian
next prev parent reply other threads:[~2002-07-24 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 13:16 Ian Soboroff
2002-07-24 13:18 ` Muli Ben-Yehuda
2002-07-24 13:46 ` Ian Soboroff
2002-07-24 14:57 ` Zwane Mwaikambo
2002-07-24 14:57 ` Ian Soboroff [this message]
2002-07-24 15:38 ` Zwane Mwaikambo
2002-07-24 16:24 ` Ian Soboroff
2002-07-24 19:09 ` Muli Ben-Yehuda
2002-08-02 14:45 ` Booting problem, 2.4.19-rc5-ac1, ali15x3 Ian Soboroff
2002-08-02 15:12 ` gigerstyle
2002-08-02 18:26 ` Go Taniguchi
2002-08-02 19:43 ` Marc Giger
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=9cffzy95g39.fsf@rogue.ncsl.nist.gov \
--to=ian.soboroff@nist.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@actcom.co.il \
--cc=zwane@linuxpower.ca \
/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®