From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
<linux-kernel@vger.kernel.org>, "NeilBrown" <neilb@suse.de>,
"Martin Schwidefsky" <schwidefsky@de.ibm.com>,
"linux-s390" <linux-s390@vger.kernel.org>
Subject: Re: 2.6.22-rc1-mm1 - s390 vs. md
Date: Fri, 18 May 2007 07:39:46 +0200 [thread overview]
Message-ID: <20070518073946.716132f4@gondolin.boeblingen.de.ibm.com> (raw)
In-Reply-To: <0C7297FA1D2D244A9C7F6959C0BF1E5201DEA0F1@azsmsx413.amr.corp.intel.com>
On Wed, 16 May 2007 23:36:56 -0700,
"Williams, Dan J" <dan.j.williams@intel.com> wrote:
> async_tx: add the Kconfig infrastructure for async_tx
>
> From: Dan Williams <dan.j.williams@intel.com>
>
> async_tx is similar to crypto in that there is an api component and a
> drivers component.
>
> * Add 'source "async_tx/Kconfig"' to the per architecture Kconfig files,
> for each architecture that sources drivers/md/Kconfig (which appears
> to be
> all of them).
> * Add 'select' statements for the subsystems that use async_tx
> (md-raid4,5)
Finer granularity is certainly better here, but I'm not quite sure if
this solves our s390 problem (we don't have dma support). All those
backends should also have a non-dma version...
next prev parent reply other threads:[~2007-05-18 5:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 6:36 Williams, Dan J
2007-05-18 5:39 ` Cornelia Huck [this message]
2007-05-18 16:30 ` Williams, Dan J
2007-05-21 7:24 ` Cornelia Huck
2007-05-21 8:52 ` Williams, Dan J
2007-05-23 0:25 ` Williams, Dan J
2007-05-23 8:05 ` Martin Schwidefsky
2007-05-23 8:46 ` Cornelia Huck
2007-05-23 8:55 ` Martin Schwidefsky
2007-05-24 22:11 ` Williams, Dan J
2007-05-25 6:02 ` Cornelia Huck
-- strict thread matches above, loose matches on Subject: below --
2007-05-16 3:19 2.6.22-rc1-mm1 Andrew Morton
2007-05-16 7:57 ` 2.6.22-rc1-mm1 - s390 vs. md Cornelia Huck
2007-05-16 17:21 ` 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=20070518073946.716132f4@gondolin.boeblingen.de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=neilb@suse.de \
--cc=schwidefsky@de.ibm.com \
/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
all inboxes | Powered by JetHome®