From: Dan Williams <dan.j.williams@intel•com>
To: Anatolij Gustschin <agust@denx•de>
Cc: "wd@denx•de" <wd@denx•de>, "dzu@denx•de" <dzu@denx•de>,
Yuri Tikhonov <yur@emcraft•com>,
"linux-raid@vger•kernel.org" <linux-raid@vger•kernel.org>,
"linuxppc-dev@ozlabs•org" <linuxppc-dev@ozlabs•org>
Subject: Re: [PATCH v3] ppc440spe-adma: adds updated ppc440spe adma driver
Date: Thu, 10 Dec 2009 23:22:28 -0700 [thread overview]
Message-ID: <4B21E524.4010601@intel.com> (raw)
In-Reply-To: <1259858161-15315-1-git-send-email-agust@denx.de>
Anatolij Gustschin wrote:
> This patch adds new version of the PPC440SPe ADMA driver.
>
> Signed-off-by: Yuri Tikhonov <yur@emcraft•com>
> Signed-off-by: Anatolij Gustschin <agust@denx•de>
> ---
>
> Changes since v2:
> - Correct Sign-offs order.
> - Place the driver in 'drivers/dma/ppc4xx' directory
> as there are wishes to extend the driver to support
> other CPUs (PPC460EX) later.
> - Don't duplicate directory name in the driver file names.
> - Perform checks for 'len' > PAGE_SIZE cases while
> looking for suitable channel for async operations
> so that there will be a fallback to synchronous path
> if a user of the api should ever submit pq_val requests
> with 'len' > PAGE_SIZE.
>
Ok, please split the katmai.dts fixups to a separate patch to send to
Josh as this patch has picked up new conflicts with his tree. It also
appears that this is not based on my next branch [1] because the
Makefile and Kconfig updates collide with the coh driver. Fix that up
and I'll apply this for my pull request for 2.6.33.
Thanks,
Dan
[1] git://git.kernel.org/pub/scm/linux/kernel/git/djbw/async_tx.git next
prev parent reply other threads:[~2009-12-11 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 16:36 [PATCH v3] ppc440spe-adma: adds updated ppc440spe adma driver Anatolij Gustschin
2009-12-11 6:22 ` Dan Williams [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=4B21E524.4010601@intel.com \
--to=dan.j.williams@intel$(echo .)com \
--cc=agust@denx$(echo .)de \
--cc=dzu@denx$(echo .)de \
--cc=linux-raid@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=wd@denx$(echo .)de \
--cc=yur@emcraft$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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