[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8bd0f97a0705221728p1c4761bbi83e58245cfca48f9@mail.gmail.com>
Date: Tue, 22 May 2007 20:28:28 -0400
From: "Mike Frysinger" <vapier.adi@...il.com>
To: "Paul Mundt" <lethal@...ux-sh.org>,
"Robin Getz" <rgetz@...ckfin.uclinux.org>,
"Bryan Wu" <bryan.wu@...log.com>, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/32] Blackfin update for 2.6.22-rc2
On 5/21/07, Paul Mundt <lethal@...ux-sh.org> wrote:
> On Mon, May 21, 2007 at 10:35:08AM -0400, Robin Getz wrote:
> > On Mon 21 May 2007 06:09, Bryan Wu pondered:
> > > Lots of update for 2.6.22-rc2 and tested on STAMP537 board.
> > >
> >
> > One of the things I noticed when trying out 2.6.22-rc1, on blackfin was:
> >
> > CALL scripts/checksyscalls.sh
> [snip syscalls]
> >
> > since there is noMMU, are we better:
> > - putting stubs (return ENOSYS - give runtime errors), or
> > - just ignore the errors - and give compile errors? (Is there any way to put
> > something into the syscall table, as not to get the warnings?)
>
> No, you'd be better of figuring out which ones you can support and which
> ones you have to -ENOSYS. CONFIG_MMU=n is not a "get out of syscalls
> free" card. Many of these have no dependency on CONFIG_MMU, anyways.
when you say -ENOSYS, do you mean we need sys_foo() that simply does
return -ENOSYS or do we just let the default syscall code go "__NR_foo
is not registered, return -ENOSYS"
-mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists