From: Dan Williams <dan.j.williams@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Shannon Nelson <shannon.nelson@intel.com>,
Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: [GIT PULL] async_tx update for 2.6.25
Date: Mon, 04 Feb 2008 13:02:50 -0700 [thread overview]
Message-ID: <1202155370.27672.3.camel@dwillia2-linux.ch.intel.com> (raw)
Linus, please pull from:
git://lost.foo-projects.org/~dwillia2/git/iop async-tx-for-linus
to receive:
Dan Williams (5):
async_tx: fix compile breakage, mark do_async_xor __always_inline
async_tx: kill ASYNC_TX_ASSUME_COHERENT
async_tx: kill tx_set_src and tx_set_dest methods
async_tx: replace 'int_en' with operation preparation flags
async_tx: allow architecture specific async_tx_find_channel implementations
Denis Cheng (2):
async_tx: use LIST_HEAD instead of LIST_HEAD_INIT
iop-adma: use LIST_HEAD instead of LIST_HEAD_INIT
crypto/async_tx/async_memcpy.c | 38 ++++-----
crypto/async_tx/async_memset.c | 28 +++---
crypto/async_tx/async_tx.c | 9 +-
crypto/async_tx/async_xor.c | 124 +++++++++++++++++-----------
drivers/dma/Kconfig | 1 +
drivers/dma/dmaengine.c | 49 +++++++-----
drivers/dma/ioat_dma.c | 43 ++++------
drivers/dma/iop-adma.c | 138 ++++++++++++--------------------
include/asm-arm/arch-iop13xx/adma.h | 18 +++--
include/asm-arm/hardware/iop3xx-adma.h | 30 ++++---
include/linux/async_tx.h | 13 ++-
include/linux/dmaengine.h | 29 ++++---
12 files changed, 259 insertions(+), 261 deletions(-)
The series is a general cleanup to the async_tx-api for 2.6.25. The
most significant change 'async_tx: kill tx_set_src and tx_set_dest
methods' removes the need to perform extra indirect calls when preparing
a descriptor. However, in order to keep the same stack footprint,
async_xor now polls for engine resources rather than simply punting to
cpu-xor.
The code was sent out for review in December [1], and has received an
Acked-by from Shannon@Intel for the parts that touch ioat_dma.
Haavard@Atmel has supplied a Reviewed-by for the pieces he felt
comfortable judging the correctness.
Regards,
Dan
[1] http://lkml.org/lkml/2007/12/21/277
reply other threads:[~2008-02-04 20:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1202155370.27672.3.camel@dwillia2-linux.ch.intel.com \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shannon.nelson@intel.com \
--cc=torvalds@linux-foundation.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