From: Greg Ungerer <gerg@snapgear.com>
To: uClinux development list <uclinux-dev@uclinux.org>
Cc: David Howells <dhowells@redhat.com>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-m68k@vger.kernel.org
Subject: Re: [uClinux-dev] Re: [PATCH] Add key management syscalls to non-i386 archs
Date: Thu, 21 Oct 2004 13:14:06 +1000 [thread overview]
Message-ID: <4177297E.6000707@snapgear.com> (raw)
In-Reply-To: <Pine.GSO.4.61.0410201840440.6837@waterleaf.sonytel.be>
Geert Uytterhoeven wrote:
> On Wed, 20 Oct 2004, David Howells wrote:
>
>>The attached patch adds syscalls for almost all archs (everything barring
>>m68knommu which is in a real mess, and i386 which already has it).
>
>
> m68nommu mirrors m68k now, but that patch doesn't seem to be in Linus' tree
> yet.
Yes, I have a patch to do that brings it into line with m68k.
I need to submit that a bunch of other patches. I am a little
behind :-)
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Dude EMAIL: gerg@snapgear.com
SnapGear -- a CyberGuard Company PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
next prev parent reply other threads:[~2004-10-21 3:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 14:44 [PATCH] Add key management syscalls to non-i386 archs David Howells
2004-10-20 14:44 ` David Howells
2004-10-20 15:29 ` Christoph Hellwig
2004-10-20 15:29 ` Christoph Hellwig
2004-10-20 17:50 ` Andrew Morton
2004-10-20 17:50 ` Andrew Morton
2004-10-20 18:18 ` Christoph Hellwig
2004-10-20 18:18 ` Christoph Hellwig
2004-10-20 15:49 ` [parisc-linux] " Matthew Wilcox
2004-10-20 15:49 ` Matthew Wilcox
2004-10-20 16:16 ` David Howells
2004-10-20 16:16 ` David Howells
2004-10-20 16:42 ` Geert Uytterhoeven
2004-10-21 3:14 ` Greg Ungerer [this message]
2004-10-20 17:08 ` Arnd Bergmann
2004-10-20 17:08 ` Arnd Bergmann
2004-10-20 22:01 ` David S. Miller
2004-10-20 22:01 ` David S. Miller
2004-10-20 22:56 ` [discuss] " Andi Kleen
2004-10-20 22:56 ` Andi Kleen
2004-10-20 23:04 ` [discuss] Re: [PATCH] Add key management syscalls to non-i386 David S. Miller
2004-10-20 23:04 ` [discuss] Re: [PATCH] Add key management syscalls to non-i386 archs David S. Miller
2004-10-20 23:25 ` Andi Kleen
2004-10-20 23:25 ` Andi Kleen
2004-10-20 23:41 ` [discuss] Re: [PATCH] Add key management syscalls to non-i386 David S. Miller
2004-10-20 23:41 ` David S. Miller
2004-10-20 23:41 ` [discuss] Re: [PATCH] Add key management syscalls to non-i386 archs David S. Miller
2004-10-20 23:41 ` David S. Miller
2004-10-21 0:10 ` Andi Kleen
2004-10-21 0:10 ` Andi Kleen
2004-10-21 8:03 ` [discuss] Re: [PATCH] Add key management syscalls to non-i386 Geert Uytterhoeven
2004-10-21 8:03 ` [discuss] Re: [PATCH] Add key management syscalls to non-i386 archs Geert Uytterhoeven
2004-10-21 1:55 ` [discuss] Re: [PATCH] Add key management syscalls to non-i386 Benjamin Herrenschmidt
2004-10-21 1:55 ` [discuss] Re: [PATCH] Add key management syscalls to non-i386 archs Benjamin Herrenschmidt
2004-10-21 8:47 ` Jan-Benedict Glaw
2004-10-21 8:47 ` Jan-Benedict Glaw
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=4177297E.6000707@snapgear.com \
--to=gerg@snapgear.com \
--cc=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=uclinux-dev@uclinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.