From: Stefan Wahren <info@lategoodbye.de>
To: "Noralf Trønnes" <noralf@tronnes.org>,
dmaengine@vger.kernel.org, vinod.koul@intel.com
Cc: dan.j.williams@intel.com, jonathan@raspberrypi.org,
linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH] dmaengine: bcm2835: Add slave dma support
Date: Fri, 17 Apr 2015 19:08:42 +0200 [thread overview]
Message-ID: <55313E1A.2040409@lategoodbye.de> (raw)
In-Reply-To: <55303318.5080609@tronnes.org>
Hi Noralf,
Am 17.04.2015 um 00:09 schrieb Noralf Trønnes:
>
> Den 15.04.2015 21:00, skrev Stefan Wahren:
>> Hi Noralf,
>>
>> Am 15.04.2015 um 11:56 schrieb Noralf Trønnes:
>>> Add slave transfer capability to BCM2835 dmaengine driver.
>>> This patch is pulled from the bcm2708-dmaengine driver in the
>>> Raspberry Pi repo. The work was done by Gellert Weisz.
>>>
>>> Tested with the bcm2835-mmc driver from the same repo.
>>
>> why not with the upstream kernel?
>>
>
> See my answer to Alexander Stein.
i read the mail, but i'm still confused. Please let me paraphrase my
last question:
Is this patch testable with upstream kernel?
It would be helpful to put those facts from the email to Alexander into
the patch description. Please clarify the intension of your patch.
Thanks
Stefan
next prev parent reply other threads:[~2015-04-17 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 9:56 [PATCH] dmaengine: bcm2835: Add slave dma support Noralf Trønnes
2015-04-15 14:37 ` Martin Sperl
2015-04-15 18:53 ` Noralf Trønnes
2015-04-16 6:30 ` Rogier Wolff
2015-04-16 17:28 ` Noralf Trønnes
2015-04-15 19:00 ` Stefan Wahren
2015-04-16 19:06 ` Alexander Stein
2015-04-16 22:03 ` Noralf Trønnes
2015-04-16 22:09 ` Noralf Trønnes
2015-04-17 17:08 ` Stefan Wahren [this message]
2015-04-17 17:19 ` Martin Sperl
2015-04-17 17:20 ` Noralf Trønnes
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=55313E1A.2040409@lategoodbye.de \
--to=info@lategoodbye.de \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=jonathan@raspberrypi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=noralf@tronnes.org \
--cc=vinod.koul@intel.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