From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Arnd Bergmann <arnd@arndb.de>,
"Linux/m68k" <linux-m68k@vger.kernel.org>,
Greg Ungerer <gerg@uclinux.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
uClinux list <uclinux-dev@uclinux.org>
Subject: Re: [PATCH] m68k: Merge mmu and non-mmu versions of sys_call_table
Date: Sat, 7 May 2011 10:34:25 +0200 [thread overview]
Message-ID: <BANLkTinssNTc_+=F4CA1Znb3bdv=c30OPw@mail.gmail.com> (raw)
In-Reply-To: <19907.2804.330120.193924@pilspetsen.it.uu.se>
On Thu, May 5, 2011 at 22:39, Mikael Pettersson <mikpe@it.uu.se> wrote:
> Geert Uytterhoeven writes:
> > On Thu, 5 May 2011, Arnd Bergmann wrote:
> > > Did you check the macros in unistd to see if they match the
> > > actual table? I guess it would be a good time to comment out
> > > the ones that are not implemented in either of the two ABIs.
> >
> > Like this?
> >
> > warning: #warning syscall pselect6 not implemented
> > warning: #warning syscall ppoll not implemented
> > warning: #warning syscall recvmmsg not implemented
> >
> > Do we need pselect6 and ppoll? I have vague memories not requiring it.
>
> They close user-space race conditions, so you want them.
So do you recommend to backport the wiring up of pselect6/ppoll to -stable?
We always had their _NR_* defines, so I guess glibc was always compiled
with pselect6/ppoll support, and will use it if it's present.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
uClinux list <uclinux-dev@uclinux.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH] m68k: Merge mmu and non-mmu versions of sys_call_table
Date: Sat, 7 May 2011 10:34:25 +0200 [thread overview]
Message-ID: <BANLkTinssNTc_+=F4CA1Znb3bdv=c30OPw@mail.gmail.com> (raw)
In-Reply-To: <19907.2804.330120.193924@pilspetsen.it.uu.se>
On Thu, May 5, 2011 at 22:39, Mikael Pettersson <mikpe@it.uu.se> wrote:
> Geert Uytterhoeven writes:
> > On Thu, 5 May 2011, Arnd Bergmann wrote:
> > > Did you check the macros in unistd to see if they match the
> > > actual table? I guess it would be a good time to comment out
> > > the ones that are not implemented in either of the two ABIs.
> >
> > Like this?
> >
> > warning: #warning syscall pselect6 not implemented
> > warning: #warning syscall ppoll not implemented
> > warning: #warning syscall recvmmsg not implemented
> >
> > Do we need pselect6 and ppoll? I have vague memories not requiring it.
>
> They close user-space race conditions, so you want them.
So do you recommend to backport the wiring up of pselect6/ppoll to -stable?
We always had their _NR_* defines, so I guess glibc was always compiled
with pselect6/ppoll support, and will use it if it's present.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
next prev parent reply other threads:[~2011-05-07 8:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 18:37 [PATCH] m68k: Merge mmu and non-mmu versions of sys_call_table Geert Uytterhoeven
2011-05-04 18:37 ` Geert Uytterhoeven
2011-05-04 22:18 ` Greg Ungerer
2011-05-04 22:18 ` Greg Ungerer
2011-05-05 6:24 ` Arnd Bergmann
2011-05-05 6:24 ` Arnd Bergmann
2011-05-05 7:55 ` Greg Ungerer
2011-05-05 7:55 ` Greg Ungerer
2011-05-05 18:44 ` Geert Uytterhoeven
2011-05-05 18:44 ` Geert Uytterhoeven
2011-05-05 20:37 ` Arnd Bergmann
2011-05-05 20:37 ` Arnd Bergmann
2011-05-06 5:11 ` Geert Uytterhoeven
2011-05-06 5:11 ` Geert Uytterhoeven
2011-05-06 8:24 ` Andreas Schwab
2011-05-06 8:24 ` Andreas Schwab
2011-05-06 18:56 ` Geert Uytterhoeven
2011-05-06 18:56 ` Geert Uytterhoeven
2011-05-05 20:39 ` Mikael Pettersson
2011-05-07 8:34 ` Geert Uytterhoeven [this message]
2011-05-07 8:34 ` Geert Uytterhoeven
2011-05-07 13:16 ` Mikael Pettersson
2011-10-23 9:53 ` Andreas Schwab
2011-10-23 12:20 ` Geert Uytterhoeven
2011-10-23 14:59 ` Andreas Schwab
2011-10-23 14:59 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2011-04-06 20:33 Geert Uytterhoeven
2011-04-07 1:53 ` Greg Ungerer
2011-04-13 18:16 ` Geert Uytterhoeven
2011-04-17 20:13 ` Arnd Bergmann
2011-04-19 4:32 ` Greg Ungerer
2011-04-19 8:21 ` Arnd Bergmann
2011-04-19 8:30 ` Geert Uytterhoeven
2011-04-19 8:52 ` Arnd Bergmann
2011-04-19 12:26 ` Greg Ungerer
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='BANLkTinssNTc_+=F4CA1Znb3bdv=c30OPw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=mikpe@it.uu.se \
--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.