Re: [PATCH 07/15] Don't return -ENOSYS as extra notes size if spufs is not loaded

2007-09-12 Thread Arnd Bergmann
On Wednesday 12 September 2007, Michael Ellerman wrote: > Because the SPU coredump code might be built as part of a module (spufs), > we have a stub which is called by the coredump code, this routine then calls > into spufs if it's loaded. > > Unfortunately the stub returns -ENOSYS if spufs is

[PATCH 07/15] Don't return -ENOSYS as extra notes size if spufs is not loaded

2007-09-12 Thread Michael Ellerman
Because the SPU coredump code might be built as part of a module (spufs), we have a stub which is called by the coredump code, this routine then calls into spufs if it's loaded. Unfortunately the stub returns -ENOSYS if spufs is not loaded, which is interpreted by the coredump code as an extra

[PATCH 07/15] Don't return -ENOSYS as extra notes size if spufs is not loaded

2007-09-12 Thread Michael Ellerman
Because the SPU coredump code might be built as part of a module (spufs), we have a stub which is called by the coredump code, this routine then calls into spufs if it's loaded. Unfortunately the stub returns -ENOSYS if spufs is not loaded, which is interpreted by the coredump code as an extra

Re: [PATCH 07/15] Don't return -ENOSYS as extra notes size if spufs is not loaded

2007-09-12 Thread Arnd Bergmann
On Wednesday 12 September 2007, Michael Ellerman wrote: Because the SPU coredump code might be built as part of a module (spufs), we have a stub which is called by the coredump code, this routine then calls into spufs if it's loaded. Unfortunately the stub returns -ENOSYS if spufs is not