From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: kuninori.morimoto.gx@renesas.com
Cc: Paul Mundt <lethal@linux-sh.org>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Liam Girdwood <lrg@ti.com>,
Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH forward] ASoC: fsi: update for dmaengine prep_slave_sg fallout.
Date: Wed, 18 Apr 2012 10:06:36 +0100 [thread overview]
Message-ID: <20120418090636.GD3021@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <87r4vl4wk2.wl%kuninori.morimoto.gx@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
On Tue, Apr 17, 2012 at 07:13:04PM -0700, kuninori.morimoto.gx@renesas.com wrote:
>
> Signed-off-by: Paul Mundt <lethal@linux-sh.org>
> Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> ---
> Nothing happened on ALSA ML.
> So I forward this patch.
> I added my Acked-by on it.
I've applied this since I can see Paul's original version in the archive
but when forwarding patches for someone else you should sign off rather
than ack the patch - signoff is mostly a statement saying "I know this
is OK legally" and so everyone who forwards the patch is supposed to add
one.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: kuninori.morimoto.gx@renesas.com
Cc: Paul Mundt <lethal@linux-sh.org>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Liam Girdwood <lrg@ti.com>,
Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH forward] ASoC: fsi: update for dmaengine prep_slave_sg fallout.
Date: Wed, 18 Apr 2012 09:06:36 +0000 [thread overview]
Message-ID: <20120418090636.GD3021@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <87r4vl4wk2.wl%kuninori.morimoto.gx@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
On Tue, Apr 17, 2012 at 07:13:04PM -0700, kuninori.morimoto.gx@renesas.com wrote:
>
> Signed-off-by: Paul Mundt <lethal@linux-sh.org>
> Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> ---
> Nothing happened on ALSA ML.
> So I forward this patch.
> I added my Acked-by on it.
I've applied this since I can see Paul's original version in the archive
but when forwarding patches for someone else you should sign off rather
than ack the patch - signoff is mostly a statement saying "I know this
is OK legally" and so everyone who forwards the patch is supposed to add
one.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-04-18 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 8:20 [PATCH] ASoC: fsi: update for dmaengine prep_slave_sg fallout Paul Mundt
2012-04-01 23:57 ` Kuninori Morimoto
2012-04-16 6:23 ` Kuninori Morimoto
2012-04-16 8:27 ` Mark Brown
2012-04-16 12:10 ` Paul Mundt
2012-04-16 12:17 ` Mark Brown
2012-04-18 2:13 ` [PATCH forward] " kuninori.morimoto.gx
2012-04-18 2:13 ` kuninori.morimoto.gx
2012-04-18 9:06 ` Mark Brown [this message]
2012-04-18 9:06 ` Mark Brown
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=20120418090636.GD3021@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.org \
--cc=lrg@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.