devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Mikhail Ulyanov <mikhail.ulyanov@cogentembedded.com>
Cc: magnus.damm@gmail.com, robh+dt@kernel.org, pawel.moll@arm.com,
	mark.rutland@arm.com, galak@codeaurora.org,
	linux@arm.linux.org.uk, laurent.pinchart@ideasonboard.com,
	sergei.shtylyov@cogentembedded.com, devicetree@vger.kernel.org,
	linux-sh@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ARM: shmobile: Add JPU device nodes to Renesas R-Car SoCs.
Date: Tue, 28 Jul 2015 09:34:53 +0900	[thread overview]
Message-ID: <20150728003453.GA21162@verge.net.au> (raw)
In-Reply-To: <1437744346-499-1-git-send-email-mikhail.ulyanov@cogentembedded.com>

On Fri, Jul 24, 2015 at 04:25:44PM +0300, Mikhail Ulyanov wrote:
> This series of patches contains device tree nodes definitions for JPEG
> codec peripheral found in the Renesas R-Car SoCs.
> 
> This series of patches is against the renesas-devel-20150720-v4.2-rc3
> of https://kernel.googlesource.com/pub/scm/linux/kernel/git/horms/renesas
> 
> The driver itself was accepted by Hans Verkuil
> http://git.linuxtv.org/cgit.cgi/hverkuil/media_tree.git
> commit hash 761a0eee505f3a7051b187e67cd28c50b385d409
> 
> Mikhail Ulyanov (2):
>   ARM: shmobile: r8a7790: Add JPU device node.
>   ARM: shmobile: r8a7791: Add JPU device node.

Thanks, I have queued up both patches.

      parent reply	other threads:[~2015-07-28  0:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 13:25 [PATCH 0/2] ARM: shmobile: Add JPU device nodes to Renesas R-Car SoCs Mikhail Ulyanov
2015-07-24 13:25 ` [PATCH 1/2] ARM: shmobile: r8a7790: Add JPU device node Mikhail Ulyanov
2015-07-24 13:25 ` [PATCH 2/2] ARM: shmobile: r8a7791: " Mikhail Ulyanov
2015-07-28  0:34 ` 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=20150728003453.GA21162@verge.net.au \
    --to=horms@verge.net.au \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=mikhail.ulyanov@cogentembedded.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).