From: Paul Mundt <lethal@linux-sh.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Vinod Koul <vinod.koul@intel.com>,
linux-kernel@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-sh@vger.kernel.org, Alan Cox <alan@linux.intel.com>
Subject: Re: [PATCH 5/9 v3] serial: sh-sci: prepare for conversion to the shdma base library
Date: Thu, 10 May 2012 12:09:39 +0900 [thread overview]
Message-ID: <20120510030938.GH7988@linux-sh.org> (raw)
In-Reply-To: <1336576161-27082-6-git-send-email-g.liakhovetski@gmx.de>
On Wed, May 09, 2012 at 05:09:17PM +0200, Guennadi Liakhovetski wrote:
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> Cc: Alan Cox <alan@linux.intel.com>
> ---
> drivers/tty/serial/sh-sci.c | 8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
Acked-by: Paul Mundt <lethal@linux-sh.org>
next prev parent reply other threads:[~2012-05-10 3:09 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 15:09 [PATCH 0/9 v3] extract an shdma base library from shdma.c Guennadi Liakhovetski
2012-05-09 15:09 ` [PATCH 1/9 v3] dmaengine: add an shdma-base library Guennadi Liakhovetski
2012-05-15 4:22 ` Vinod Koul
2012-05-18 8:21 ` Guennadi Liakhovetski
2012-05-25 8:15 ` Vinod Koul
2012-05-25 8:30 ` Guennadi Liakhovetski
2012-06-28 8:52 ` Guennadi Liakhovetski
2012-07-02 20:28 ` Guennadi Liakhovetski
2012-07-02 20:30 ` [PATCH 0.5/9] dma: move shdma driver to an own directory Guennadi Liakhovetski
2012-07-13 3:26 ` [PATCH 1/9 v3] dmaengine: add an shdma-base library Vinod Koul
2012-07-16 5:58 ` Vinod Koul
2012-05-25 10:27 ` Laxman Dewangan
2012-05-25 10:59 ` Guennadi Liakhovetski
2012-05-09 15:09 ` [PATCH 2/9 v3] dma: shdma: prepare for conversion to the shdma base library Guennadi Liakhovetski
2012-05-15 4:23 ` Vinod Koul
2012-05-18 8:21 ` Guennadi Liakhovetski
2012-05-09 15:09 ` [PATCH 3/9 v3] mmc: sh_mmcif: remove unneeded struct sh_mmcif_dma, prepare to shdma conversion Guennadi Liakhovetski
2012-07-05 17:35 ` Chris Ball
2012-05-09 15:09 ` [PATCH 4/9 v3] mmc: sh_mobile_sdhi: prepare for conversion to the shdma base library Guennadi Liakhovetski
2012-07-05 17:37 ` Chris Ball
2012-05-09 15:09 ` [PATCH 5/9 v3] serial: sh-sci: " Guennadi Liakhovetski
2012-05-10 3:09 ` Paul Mundt [this message]
2012-05-15 4:27 ` Vinod Koul
2012-05-18 8:21 ` Guennadi Liakhovetski
2012-05-09 15:09 ` [PATCH 6/9 v3] ASoC: siu: " Guennadi Liakhovetski
2012-05-09 15:37 ` Mark Brown
2012-05-09 15:09 ` [PATCH 7/9 v3] usb: renesas_usbhs: " Guennadi Liakhovetski
2012-05-09 23:59 ` kuninori.morimoto.gx
2012-05-10 0:07 ` Greg Kroah-Hartman
2012-05-09 15:09 ` [PATCH 8/9 v3] ASoC: fsi: " Guennadi Liakhovetski
2012-05-09 15:39 ` Mark Brown
2012-05-09 23:59 ` kuninori.morimoto.gx
2012-05-09 15:09 ` [PATCH 9/9 v3] dma: shdma: convert " Guennadi Liakhovetski
2012-07-25 3:59 ` Paul Mundt
2012-07-26 6:49 ` Vinod Koul
2012-07-26 6:58 ` Paul Mundt
2012-07-26 11:20 ` Vinod Koul
2012-07-26 21:39 ` Guennadi Liakhovetski
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=20120510030938.GH7988@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=alan@linux.intel.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=vinod.koul@intel.com \
--cc=yoshihiro.shimoda.uh@renesas.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