From: Dan Malek <dan@embeddededge.com>
To: Eugene Surovegin <ebs@innocent.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: consistent_alloc from an interrupt context
Date: Thu, 13 Jun 2002 01:06:14 -0400 [thread overview]
Message-ID: <3D082846.4080005@embeddededge.com> (raw)
In-Reply-To: 5.1.0.14.2.20020612211908.02c7b0e8@mail.attbi.com
Eugene Surovegin wrote:
> I thought of it, but is it OK to modify arch-independent code with such
> a hack?
It's OK in your own code, I probably still have some around that looks
like that :-)
> Maybe this is the reason it never was accepted.
I'll have to search for the messages where this was discussed and see what
happened. I know it wasn't discussed on the PowerPC lists, it was on some
other processor I was using. I was just able to make the same changes and
test it on 8xx as well.
> Though, it's obviously much simpler than solution I used :)
Hey, whatever works......it's a hacker's world :-)
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-06-13 5:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-13 3:22 consistent_alloc from an interrupt context Eugene Surovegin
2002-06-13 4:05 ` Dan Malek
2002-06-13 4:24 ` Eugene Surovegin
2002-06-13 5:06 ` Dan Malek [this message]
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=3D082846.4080005@embeddededge.com \
--to=dan@embeddededge.com \
--cc=ebs@innocent.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).