mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	Vinod Koul <vinod.koul@intel.com>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	linux-sh@vger.kernel.org, dmaengine@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] dmaengine: shdma: Register documentation
Date: Fri, 11 Jul 2014 10:31:42 +0200	[thread overview]
Message-ID: <20140711083142.GB22753@verge.net.au> (raw)
In-Reply-To: <1403267861-15609-1-git-send-email-geert+renesas@glider.be>

Hi Geert,

in order to try and create a smoother path for changes in this area to land
I have pushed them to the shdma-for-v3.17 branch of my renesas tree
on kernel.org. It is merged into the devel and next branches of that tree
and should appear in linux-next in the near future.

My intention is to send a pull-request for this branch once it has sat
in next for a short time. I hope that this approach is useful to all parties.

On Fri, Jun 20, 2014 at 02:37:37PM +0200, Geert Uytterhoeven wrote:
> This patch series adds more register documentation for shdma, and replaces
> some hardcoded numbers by defines.
> 
>   [1/4] dmaengine: shdma: Add more register documentation
>   [2/4] ARM: shmobile: dma: Use defines instead of hardcoded numbers
>   [3/4] sh: dma: Use defines instead of hardcoded numbers
>   [4/4] dmaengine: shdma: Use defines instead of hardcoded numbers
> 
>  arch/arm/mach-shmobile/dma-register.h  |  4 +--
>  arch/sh/drivers/dma/dma-sh.c           |  2 +-
>  arch/sh/include/asm/dma-register.h     | 36 ++++++++++---------
>  arch/sh/kernel/cpu/sh4a/setup-sh7722.c | 24 ++++++-------
>  arch/sh/kernel/cpu/sh4a/setup-sh7724.c | 48 ++++++++++++-------------
>  arch/sh/kernel/cpu/sh4a/setup-sh7757.c | 64 +++++++++++++++++-----------------
>  drivers/dma/sh/shdma-arm.h             |  4 +--
>  drivers/dma/sh/shdmac.c                | 15 ++++----
>  include/linux/sh_dma.h                 | 24 +++++++------
>  9 files changed, 112 insertions(+), 109 deletions(-)
> 
> Thanks!
> 
> Gr{oetje,eeting}s,
> 
> 						Geert
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> 							    -- Linus Torvalds
> 

      parent reply	other threads:[~2014-07-11 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 12:37 Geert Uytterhoeven
2014-06-20 12:37 ` [PATCH 1/4] dmaengine: shdma: Add more register documentation Geert Uytterhoeven
2014-06-20 12:37 ` [PATCH 2/4] ARM: shmobile: dma: Use defines instead of hardcoded numbers Geert Uytterhoeven
2014-07-15  9:02   ` Simon Horman
2014-06-20 12:37 ` [PATCH 3/4] sh: " Geert Uytterhoeven
2014-06-20 12:37 ` [PATCH 4/4] dmaengine: shdma: " Geert Uytterhoeven
2014-07-11  8:31 ` Simon Horman [this message]

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=20140711083142.GB22753@verge.net.au \
    --to=horms@verge.net.au \
    --cc=dmaengine@vger.kernel.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=geert+renesas@glider.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --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

all inboxes | Powered by JetHome®