All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	linux-kernel@vger.kernel.org
Subject: Re: [-mm patch] the ASYNC_* options shouldn't be user visible
Date: Mon, 4 Jun 2007 21:20:02 +0200	[thread overview]
Message-ID: <20070604192000.GZ5500@stusta.de> (raw)
In-Reply-To: <0C7297FA1D2D244A9C7F6959C0BF1E5201F0351F@azsmsx413.amr.corp.intel.com>

On Mon, Jun 04, 2007 at 11:25:02AM -0700, Williams, Dan J wrote:
> > From: Williams, Dan J
> > >
> > > BTW: Please move the async_tx directory under drivers/ or lib/
> > >
> One caveat with this... md.o needs xor.o to be initialized first.
> Moving xor.o under lib/ means this assumption is broken since the
> top-level Makefile puts 'libs' after 'drivers'.
>...

What about using a different initcall level?

Depending on the link order is not such a good idea.

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:[~2007-06-04 19:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04 18:25 [-mm patch] the ASYNC_* options shouldn't be user visible Williams, Dan J
2007-06-04 19:20 ` Adrian Bunk [this message]
2007-06-04 22:34   ` Williams, Dan J
2007-06-04 21:33 ` Herbert Xu
  -- strict thread matches above, loose matches on Subject: below --
2007-05-31  6:58 2.6.22-rc3-mm1 Andrew Morton
2007-06-02 19:09 ` [-mm patch] the ASYNC_* options shouldn't be user visible Adrian Bunk
2007-06-04 16:19   ` Williams, Dan J

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=20070604192000.GZ5500@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --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 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.