From: "Sarnath Kannan" <sparc64@rediffmail.com>
To: "Dan Malek" <dan@embeddededge.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Re: "OpenPIC versus EPIC" in MPC8240 !
Date: 13 Nov 2001 04:00:33 -0000 [thread overview]
Message-ID: <20011113040033.14692.qmail@mailweb29.rediffmail.com> (raw)
> It's only a bug if we don't know we are doing this and
> it is causing problems. We know we can do what we
> are doing without trouble. I'm not trying to
> justify this hack or claim it is the proper solution.
> It just happens to work, allows us to take advantage of
> existing software functions, and someday it may be
> changed.
Yeah fine Dan ! First time, I thought these
details were left out. But later only I realized
that these things have been foreseen and deliberately
taken advantage of. I apologize for all the
trouble.
Sarnath
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-11-13 4:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 4:00 Sarnath Kannan [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-12 8:41 Re: "OpenPIC versus EPIC" in MPC8240 ! Sarnath Kannan
2001-11-07 14:11 Sarnath Kannan
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=20011113040033.14692.qmail@mailweb29.rediffmail.com \
--to=sparc64@rediffmail.com \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@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).