From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org,
monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
liqin.chen-+XGAvkf1AAHby3iVrkZq2A@public.gmane.org,
Sam Ravnborg <sam-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org>,
Remis Lima Baima
<remis.developer-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Subject: [RFC 00/17] asm-generic ABI files for microblaze
Date: Mon, 27 Apr 2009 16:40:43 +0200 [thread overview]
Message-ID: <200904271640.44445.arnd@arndb.de> (raw)
This is my attempt to do a generic system call ABI for
all new architectures, including a port for microblaze,
which has recently been merged into 2.6.30. The next
architecture that is about to get merged will be score,
so it would be good if they can move to the same ABI.
Please review the files and (in case of microblaze
and score maintainers) test them on your architecture.
The one part I'm not yet completely happy with is signal
handling, I had to massage the microblaze code quite a
bit to get the old-style siginfo out of it, which may
not yet work.
Sam also mentioned that it might be good to consistently
use the __u32 and similar types everywhere in asm-generic
exported headers, which I might be doing as a next step
(including the existing files).
Special thanks to Remis Baima, who has done some significant
work cleaning up my patches.
Arnd <><
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: linux-kernel@vger.kernel.org
Cc: john.williams@petalogix.com, monstr@monstr.eu,
linux-api@vger.kernel.org, linux-arch@vger.kernel.org,
liqin.chen@sunplusct.com, Sam Ravnborg <sam@ravnborg.org>,
Remis Lima Baima <remis.developer@googlemail.com>
Subject: [RFC 00/17] asm-generic ABI files for microblaze
Date: Mon, 27 Apr 2009 16:40:43 +0200 [thread overview]
Message-ID: <200904271640.44445.arnd@arndb.de> (raw)
Message-ID: <20090427144043.6NR5kSibzY5KwfyhmZx_hAL4FpOgrtAwY2aDjbG5dEk@z> (raw)
This is my attempt to do a generic system call ABI for
all new architectures, including a port for microblaze,
which has recently been merged into 2.6.30. The next
architecture that is about to get merged will be score,
so it would be good if they can move to the same ABI.
Please review the files and (in case of microblaze
and score maintainers) test them on your architecture.
The one part I'm not yet completely happy with is signal
handling, I had to massage the microblaze code quite a
bit to get the old-style siginfo out of it, which may
not yet work.
Sam also mentioned that it might be good to consistently
use the __u32 and similar types everywhere in asm-generic
exported headers, which I might be doing as a next step
(including the existing files).
Special thanks to Remis Baima, who has done some significant
work cleaning up my patches.
Arnd <><
next reply other threads:[~2009-04-27 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 14:40 Arnd Bergmann [this message]
2009-04-27 14:40 ` [RFC 00/17] asm-generic ABI files for microblaze Arnd Bergmann
[not found] ` <200904271640.44445.arnd-r2nGTMty4D4@public.gmane.org>
2009-04-27 15:12 ` Sam Ravnborg
2009-04-27 15:12 ` Sam Ravnborg
[not found] ` <20090427151241.GA10558-QabhHTsIXMSnlFQ6Q1D1Y0B+6BGkLq7r@public.gmane.org>
2009-04-27 15:15 ` Arnd Bergmann
2009-04-27 15:15 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2009-04-27 15:01 arnd-r2nGTMty4D4
2009-04-27 15:01 ` arnd
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=200904271640.44445.arnd@arndb.de \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=liqin.chen-+XGAvkf1AAHby3iVrkZq2A@public.gmane.org \
--cc=monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org \
--cc=remis.developer-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
--cc=sam-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.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