From: Grant Grundler <grundler@parisc-linux.org>
To: Joel Soete <jsoe0708@tiscali.be>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] warning: minor abi change
Date: Fri, 27 Jun 2003 10:54:51 -0600 [thread overview]
Message-ID: <20030627165451.GB371@dsl2.external.hp.com> (raw)
In-Reply-To: <3ED70CF10000AE2E@ocpmta2.freegates.net>
Joel,
I mistakenly replied only to you on my previous mail.
Can you please forward my previous reply to parisc-linux mailing list
or send a copy back to me - I'll post it to the list then.
On Fri, Jun 27, 2003 at 06:14:58PM +0200, Joel Soete wrote:
> Hi Grant,
>
> > diff -NaurX dontdiff linux-2.4.21-pa0/drivers/ide/pci/ns87415.c linux-2.4.21-rc8-pa35/drivers/ide/pci/ns87415.c
>
> > This is for c3000/j5000/et al workstations.
> > NS "SuckyIO" multifunction chip includes ns87415 compatible IDE controller.
>
> ...
> >> +#define __save_and_cli(x) do { __save_flags(x); __cli(); } while(0);
> >> +#define __save_and_sti(x) do { __save_flags(x); __sti(); } while(0);
> >> +
>
> > This is something different - but I'd think this is needed too.
> > Make sure this isn't a merge error (ie see if it's defined elsewhere).
>
> I need it to make work my ide cdrom onto my b2k (I grab this stuff
> from another platform)
ah ok.
The IDE CDROM are pretty standard devices. Note the DMA does NOT work.
And even with PIO mode, it just barely works - enough to do an install.
So don't use it too much unless you can afford to crash your box.
At least that was my experience with 2.4.19 or so.
> The following stuff is just a variant (just for info)
ok.
...
> > If they are no longer referenced, that's fine.
> hmm in fact the last ref of 'cpu_irq_actions' is in arch/parisc/kernel/processor.c
> and now embrace by #if 0 [...] #endif
> (I will see to cleanup too)
> ...
ok
>
> > I need the above changes in a format that I apply with "patch -p1 < diff"
>
> Here is attached Mydiff2421.txt
ok. let me apply local and try it out first. If all is well, should see
something by this weekend.
thanks,
grant
next parent reply other threads:[~2003-06-27 16:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030627151546.GA30607@dsl2.external.hp.com>
[not found] ` <3ED70CF10000AE2E@ocpmta2.freegates.net>
2003-06-27 16:54 ` Grant Grundler [this message]
2003-06-28 10:48 ` [parisc-linux] warning: minor abi change Joel Soete
2003-07-05 23:08 ` Grant Grundler
2003-07-05 23:53 ` John David Anglin
2003-07-06 4:12 ` Grant Grundler
2003-07-06 16:12 ` Joel Soete
2003-07-07 20:02 ` Carlos O'Donell
2003-07-07 20:19 ` John David Anglin
2003-07-08 1:45 ` Carlos O'Donell
2003-07-06 5:57 ` [parisc-linux] IDE modules build prob Grant Grundler
2003-07-06 6:31 ` Grant Grundler
2003-07-06 7:23 ` Alan Cox
[not found] <20030711065156.GA17025@dsl2.external.hp.com>
2003-07-11 8:26 ` [parisc-linux] warning: minor abi change Joel Soete
2003-07-11 10:24 ` Alan Cox
2003-06-26 13:54 Matthew Wilcox
2003-06-26 17:03 ` Joel Soete
2003-06-26 17:06 ` Matthew Wilcox
2003-06-26 17:45 ` Randolph Chung
2003-06-27 14:41 ` Joel Soete
2003-06-27 16:21 ` Joel Soete
2003-06-27 16:52 ` Alan Cox
2003-07-07 16:00 ` Joel Soete
2003-07-07 16:05 ` Alan Cox
2003-07-07 16:31 ` Matthew Wilcox
2003-07-07 16:39 ` Joel Soete
2003-07-07 16:33 ` Joel Soete
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=20030627165451.GB371@dsl2.external.hp.com \
--to=grundler@parisc-linux.org \
--cc=jsoe0708@tiscali.be \
--cc=parisc-linux@lists.parisc-linux.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