From: Benjamin Herrenschmidt <bh40@calva.net>
To: Gavin Hemphill <hemphill@drea.dnd.ca>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: mprotect and SMP
Date: Thu, 7 Dec 2000 14:15:05 +0100 [thread overview]
Message-ID: <19341101064649.16824@192.168.1.2> (raw)
In-Reply-To: <3A2F82B3.46C4C2E0@drea.dnd.ca>
>
>This problem has existed since the earliest kernels I've had for the
>gemini (about 2.2.13).
>
>I've got read access to the bk tree now, the problem is that it doesn't
>boot when configured for the gemini, I'm going to look through the
>gemini specific diffs and try and get the 2_2 tree running, but from
>what I've seen in the larger set of diff's there's no modifications that
>seem to apply to the mprotect problem. Just out of curiosity, if I do
>get the gemini configuration running who do I send the changes to so
>that they make it back into the tree.
> Gavin
Send them to this list, CC to me & paulus, eventually submit them to the
sourceforge site.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-12-07 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 16:08 mprotect and SMP Gavin Hemphill
2000-12-06 21:52 ` Benjamin Herrenschmidt
2000-12-07 12:29 ` Gavin Hemphill
2000-12-07 13:15 ` Benjamin Herrenschmidt [this message]
2001-01-03 1:35 ` Gavin Hemphill
2000-12-07 17:16 ` Gavin Hemphill
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=19341101064649.16824@192.168.1.2 \
--to=bh40@calva.net \
--cc=hemphill@drea.dnd.ca \
--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).