From: John Richard Moser <nigelenki@comcast.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Montavista Realtime compilation failures
Date: Wed, 15 Dec 2004 14:36:36 -0500 [thread overview]
Message-ID: <41C09244.2030403@comcast.net> (raw)
In-Reply-To: <20041215094954.GA19147@infradead.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ahh, alright, sorry. I remember they announced this stuff to the list,
so I thought it had reached the general interest of the LKML.
Christoph Hellwig wrote:
| On Wed, Dec 15, 2004 at 01:01:11AM -0500, John Richard Moser wrote:
|
|>-----BEGIN PGP SIGNED MESSAGE-----
|>Hash: SHA1
|>
|>The MontaVista patches[1] I applied to 2.6.9 are not compiling on
|>x86_64. I'm also using a PaX pre-patch, which I don't believe is
|>interfering; there were collisions with PaX in mm/, but none of those
|>show here (they were all in .c files, not headers, so they cannot have
|>an impact here).
|
|
| I think you're much better off complaining to mvista.
|
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBwJJDhDd4aOud5P8RAt7XAJ9LQMN8aku8f+rhmavV9MEOjH5x3gCfaHXS
By0aLOAzXPwj2YwrtopKIqQ=
=9J4g
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-12-15 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 6:01 Montavista Realtime compilation failures John Richard Moser
2004-12-15 6:07 ` John Richard Moser
2004-12-15 9:49 ` Christoph Hellwig
2004-12-15 19:36 ` John Richard Moser [this message]
2004-12-15 19:44 ` Lee Revell
2004-12-16 16:39 ` Tom Rini
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=41C09244.2030403@comcast.net \
--to=nigelenki@comcast.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.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