[RFC 00/17] asm-generic ABI files for microblaze

[RFC 00/17] asm-generic ABI files for microblaze

[Arnd Bergmann]

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

[RFC 00/17] asm-generic ABI files for microblaze

[arnd-r2nGTMty4D4]

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.
Sorry for spamming everyone with the broken mail headers.
I hope this resend does fly better.

	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

Re: [RFC 00/17] asm-generic ABI files for microblaze

[Sam Ravnborg]

On Mon, Apr 27, 2009 at 04:40:43PM +0200, Arnd Bergmann wrote:
> 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 submission is seriously broken.
- subject is missing
- reply-to-all is broken

Can you resend with this fixed, then it makes review easier.

	Sam
--
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

Re: [RFC 00/17] asm-generic ABI files for microblaze

[Arnd Bergmann]

On Monday 27 April 2009, Sam Ravnborg wrote:
> The submission is seriously broken.
> - subject is missing
> - reply-to-all is broken
> 
> Can you resend with this fixed, then it makes review easier.
> 

Sure, I have already done this and identified the problem: I had
an extra '>' character in the description file I entered in quilt
mail. For some reason, kmail still showed the patches correctly,
by they got corrupted on the way out anyway. I'll look into
using git-send-email in the future.

	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