From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 01/10] DMA: pl330: support burst mode for dev-to-mem and mem-to-dev transmit
Date: Thu, 15 Oct 2015 09:38:22 +0530 [thread overview]
Message-ID: <20151015040821.GD27370@localhost> (raw)
In-Reply-To: <1444872912-2215-1-git-send-email-shawn.lin@rock-chips.com>
On Thu, Oct 15, 2015 at 09:35:12AM +0800, Shawn Lin wrote:
> From: Boojin Kim <boojin.kim@samsung.com>
>
Please fix the subsystem name in this series. Its dmaengine:...
Git log should tell you the acceptable style for a subsystem
--
~Vinod
next prev parent reply other threads:[~2015-10-15 4:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 1:34 [PATCH v6 0/10] Fix broken DMAFLUSHP on Rockchips platform Shawn Lin
2015-10-15 1:35 ` [PATCH v6 01/10] DMA: pl330: support burst mode for dev-to-mem and mem-to-dev transmit Shawn Lin
2015-10-15 4:08 ` Vinod Koul [this message]
2015-10-15 6:51 ` Shawn Lin
2015-10-15 1:35 ` [PATCH v6 02/10] Documentation: arm-pl330: add description of arm, pl330-broken-no-flushp Shawn Lin
2015-10-15 1:35 ` [PATCH v6 03/10] DMA: pl330: add quirk for broken no flushp Shawn Lin
2015-10-15 1:35 ` [PATCH v6 04/10] ARM: dts: Add arm, pl330-broken-no-flushp quirk for rk3288 platform Shawn Lin
2015-10-15 1:35 ` [PATCH v6 05/10] ARM: dts: Add arm, pl330-broken-no-flushp quirk for rk3xxx platform Shawn Lin
2015-10-15 1:36 ` [PATCH v6 06/10] DMA: dmaengine: expose max burst capability to clients Shawn Lin
2015-10-15 1:36 ` [PATCH v6 07/10] DMA: pl330: add max burst for dmaengine Shawn Lin
2015-10-15 1:36 ` [PATCH v6 08/10] spi: rockchip: modify DMA max burst to 1 Shawn Lin
2015-10-15 1:36 ` [PATCH v6 09/10] snd: dmaengine-pcm: add snd_dmaengine_pcm_get_caps interface Shawn Lin
2015-10-15 3:07 ` [alsa-devel] " kbuild test robot
2015-10-15 4:05 ` Vinod Koul
2015-10-15 6:50 ` Shawn Lin
2015-10-15 1:36 ` [PATCH v6 10/10] ASoC: rockchip_i2s: modify DMA max burst to 1 Shawn Lin
2015-10-15 3:20 ` kbuild test robot
2015-10-15 8:53 ` Lars-Peter Clausen
2015-10-15 10:47 ` Jianqun Xu
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=20151015040821.GD27370@localhost \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.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).