public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] deprecate the tasklist_lock export
Date: Fri, 17 Feb 2006 21:12:38 +0100	[thread overview]
Message-ID: <20060217201238.GK4422@stusta.de> (raw)
In-Reply-To: <20060217112355.GE28448@lst.de>

On Fri, Feb 17, 2006 at 12:23:55PM +0100, Christoph Hellwig wrote:
> On Wed, Feb 15, 2006 at 10:48:33PM +0100, Adrian Bunk wrote:
> > On Wed, Feb 15, 2006 at 02:07:34PM +0100, Christoph Hellwig wrote:
> > > Drivers have no business looking at the task list and thus using this
> > > lock.  The only possibly modular users left are:
> > > 
> > >  arch/ia64/kernel/mca.c
> > >...
> > >  fs/binfmt_elf.c
> > > 
> > > which I'll send out fixes for soon.
> > >...
> > 
> > These two can't be built modular.
> 
> s390 and sparc64 allows a modular BINFMT_ELF32, which #includes
> fs/binfmt_elf.c after redefining various things.  But I suspect the
> right fix for this is to disallow building it modular..
>...

Argh, I hate code #include'ing .c files.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-02-17 20:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 13:07 [PATCH] deprecate the tasklist_lock export Christoph Hellwig
2006-02-15 14:09 ` Steven Rostedt
2006-02-17 11:20   ` Christoph Hellwig
2006-02-17 12:31     ` Steven Rostedt
2006-02-15 21:48 ` Adrian Bunk
2006-02-17 11:23   ` Christoph Hellwig
2006-02-17 20:12     ` Adrian Bunk [this message]
2006-02-16 20:50 ` Olaf Titz

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=20060217201238.GK4422@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=hch@lst.de \
    --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