public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@convergence.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: arjanv@redhat.com, linux-kernel@vger.kernel.org,
	Dave Jones <davej@redhat.com>
Subject: Re: [PATCH] further __KERNEL_SYSCALLS__ removal
Date: Sat, 28 Feb 2004 23:39:41 +0100	[thread overview]
Message-ID: <20040228223941.GC1994@convergence.de> (raw)
In-Reply-To: <200402271957.47235.arnd@arndb.de>

On Fri, Feb 27, 2004 at 07:57:47PM +0100, Arnd Bergmann wrote:
> On Friday 27 February 2004 19:00, Arjan van de Ven wrote:
> > On Fri, 2004-02-27 at 18:35, Arnd Bergmann wrote:
> > > ===== drivers/media/dvb/frontends/alps_tdlb7.c 1.8 vs edited =====
> > > --- 1.8/drivers/media/dvb/frontends/alps_tdlb7.c	Thu Feb 26 03:09:55 2004
> > > +++ edited/drivers/media/dvb/frontends/alps_tdlb7.c	Thu Feb 26 23:57:05
> 
> >
> > this is the wrong way to "fix" this; might as well leave this driver as
> > is until it is fixed to use request_firmware()
> 
> My idea was to finally eliminate __KERNEL_SYSCALLS__ without breaking
> the in-tree drivers, so I changed all I could.
> This patch leaves the syscalls in device drivers and fixes all
> necessary uses in init/*.c.
> Maybe we can find a better solution for calling execve in do_linuxrc(),
> run_init_process() and ____call_usermodehelper(). Then a #warning can
> be added __KERNEL_SYSCALLS__ is defined.

Michael Hunold already has some patches to change DVB to
use the kernel I2C stuff, so we can then convert frontends
to use request_firmware() properly. However, this work
is not finished yet, and needs more testing.

Johannes

      reply	other threads:[~2004-02-28 22:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27 17:35 [PATCH] further __KERNEL_SYSCALLS__ removal Arnd Bergmann
2004-02-27 18:00 ` Arjan van de Ven
2004-02-27 18:57   ` Arnd Bergmann
2004-02-28 22:39     ` Johannes Stezenbach [this message]

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=20040228223941.GC1994@convergence.de \
    --to=js@convergence.de \
    --cc=arjanv@redhat.com \
    --cc=arnd@arndb.de \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.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