From: Dan Malek <dmalek@jlc.net>
To: kd@flaga.is
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: MPX860 : MBX_IMAP_ADDR undefined
Date: Fri, 18 Dec 1998 13:15:02 -0500 [thread overview]
Message-ID: <367A9BA6.1FDD4CE7@jlc.net> (raw)
In-Reply-To: 002566DC.006770DB.00@notes.flaga.is
kd@flaga.is wrote:
> ...... Unfortunately this fails on arch/ppc/kernel/irq.c
> because of MBX_IMAP_ADDR undefined
Really? It should simply be IMAP_ADDR now. The sources
I downloaded a few days ago were correct. Are you sure
you downloaded the right stuff from the right place?
-- Dan
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1998-12-18 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-16 18:49 MPX860 : MBX_IMAP_ADDR undefined kd
1998-12-18 18:15 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-12-19 14:15 kd
1998-12-19 21:02 ` Dan Malek
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=367A9BA6.1FDD4CE7@jlc.net \
--to=dmalek@jlc.net \
--cc=kd@flaga.is \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).