From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alexander Popov <a13xp0p0v88@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
devicetree-discuss@lists.ozlabs.org, Timur Tabi <timur@tabi.org>,
Rob Herring <rob.herring@calxeda.com>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Grant Likely <grant.likely@linaro.org>,
Anatolij Gustschin <agust@denx.de>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2] powerpc/512x: DMA via LocalPlus Bus testing driver
Date: Thu, 16 May 2013 18:15:23 -0700 [thread overview]
Message-ID: <20130517011523.GA9555@kroah.com> (raw)
In-Reply-To: <1367508195-2420-1-git-send-email-a13xp0p0v88@gmail.com>
On Thu, May 02, 2013 at 07:23:15PM +0400, Alexander Popov wrote:
> This module tests Direct Memory Access to some device on LocalPlus Bus
> for Freescale MPC512x. In other words it tests the bundle
> of mpc512x_lpbfifo and mpc512x_dma drivers.
>
> This testing driver was multiply used with static RAM (CY62167EV30LL-45ZXI)
> which lives on LocalPlus Bus on our board. This testing driver was used
> instead of the original static RAM driver and it is an abnormal hack.
> That is why I just provide the driver code and don't modify any environment.
>
> Signed-off-by: Alexander Popov <a13xp0p0v88@gmail.com>
> ---
> drivers/misc/mpc512x_lpbdma_test.c | 310 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 310 insertions(+)
> create mode 100644 drivers/misc/mpc512x_lpbdma_test.c
You obviously didn't test your testing driver to see if it would build
in the kernel source tree :(
Care to try again?
next prev parent reply other threads:[~2013-05-17 3:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 15:23 [PATCH 2/2] powerpc/512x: DMA via LocalPlus Bus testing driver Alexander Popov
2013-05-17 1:15 ` Greg Kroah-Hartman [this message]
2013-05-17 6:53 ` Alexander Popov
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=20130517011523.GA9555@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=a13xp0p0v88@gmail.com \
--cc=agust@denx.de \
--cc=arnd@arndb.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=rob.herring@calxeda.com \
--cc=timur@tabi.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