From: David Miller <davem@davemloft.net>
To: dan.j.williams@intel.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
christopher.leech@intel.com
Subject: Re: [RFC PATCH 0/2] dmaengine: preparation for raid acceleration
Date: Wed, 27 Jun 2007 00:54:16 -0700 (PDT) [thread overview]
Message-ID: <20070627.005416.43852201.davem@davemloft.net> (raw)
In-Reply-To: <20070602001527.1707.58092.stgit@dwillia2-linux.ch.intel.com>
From: Dan Williams <dan.j.williams@intel.com>
Date: Fri, 01 Jun 2007 17:17:49 -0700
> Hello David,
>
> The following two patches are part of the raid acceleration series I
> would like to push for 2.6.23 consideration. I am sending these two
> separately for your review for the following reasons: the 'dmaengine'
> core initially came in through netdev, patch #2 makes changes to
> net/dev/core.c, and lastly I have an ack on the raid changes but no ack
> from the community on the i/oat and dmaengine changes.
>
> dmaengine: add base support for the async_tx api
> dmaengine: move channel management to the client
Dan, you can merge this through Andrew's -mm tree and this
will actually make things easier for me. The net changes
are minimal and I have no problem with them.
Acked-by: David S. Miller <davem@davemloft.net>
prev parent reply other threads:[~2007-06-27 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 0:17 [RFC PATCH 0/2] dmaengine: preparation for raid acceleration Dan Williams
2007-06-02 0:17 ` [RFC PATCH 1/2] dmaengine: add base support for the async_tx api Dan Williams
2007-06-02 0:17 ` [RFC PATCH 2/2] dmaengine: move channel management to the client Dan Williams
2007-06-27 7:54 ` David Miller [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=20070627.005416.43852201.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=christopher.leech@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).