From: Simon Horman <horms@verge.net.au>
To: Mikhail Ulyanov <mikhail.ulyanov@cogentembedded.com>
Cc: hverkuil@xs4all.nl, magnus.damm@gmail.com, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
mchehab@osg.samsung.com, laurent.pinchart@ideasonboard.com,
j.anaszewski@samsung.com, kamil@wypas.org,
sergei.shtylyov@cogentembedded.com, devicetree@vger.kernel.org,
linux-media@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/3] R-Car JPEG Processing Unit
Date: Wed, 22 Jul 2015 09:41:05 +0900 [thread overview]
Message-ID: <20150722004105.GD25644@verge.net.au> (raw)
In-Reply-To: <1437444022-28916-1-git-send-email-mikhail.ulyanov@cogentembedded.com>
Hi Mikhail,
On Tue, Jul 21, 2015 at 05:00:19AM +0300, Mikhail Ulyanov wrote:
> This series of patches contains a driver for the JPEG codec integrated
> peripheral found in the Renesas R-Car SoCs and associated DT documentation.
I am wondering if you have any plans to post patches to integrate this
change on any Reneas boards - by which I mean patches to update dts and/or
dtsi files. I would be very happy to see such patches submitted for review.
next prev parent reply other threads:[~2015-07-22 0:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 2:00 [PATCH 0/3] R-Car JPEG Processing Unit Mikhail Ulyanov
2015-07-21 2:00 ` [PATCH v5 1/3] V4L2: platform: Add Renesas R-Car JPEG codec driver Mikhail Ulyanov
2015-07-21 2:00 ` [PATCH v3 2/3] devicetree: bindings: Document Renesas R-Car JPEG Processing Unit Mikhail Ulyanov
2015-07-21 2:00 ` [PATCH 3/3] MAINTAINERS: V4L2: PLATFORM: Add entry for Renesas JPEG Processing Unit driver Mikhail Ulyanov
2015-07-22 0:41 ` Simon Horman [this message]
2015-07-22 1:19 ` [PATCH 0/3] R-Car JPEG Processing Unit Mikhail Ulyanov
2015-07-22 1:40 ` Simon Horman
2015-07-22 6:08 ` Hans Verkuil
-- strict thread matches above, loose matches on Subject: below --
2015-07-22 11:23 Mikhail Ulyanov
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=20150722004105.GD25644@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=j.anaszewski@samsung.com \
--cc=kamil@wypas.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mchehab@osg.samsung.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