devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-samsung-soc@vger.kernel.org,
	Andrzej Pietrasiewicz <andrzej.p@samsung.com>,
	Pawel Moll <Pawel.Moll@arm.com>,
	Mark Rutland <Mark.Rutland@arm.com>,
	Kumar Gala <galak@codeaurora.org>,
	Rob Herring <rob.herring@calxeda.com>
Subject: Re: [PATCH] s5p-jpeg: Add initial device tree support for S5PV210/Exynos4210 SoCs
Date: Tue, 27 Aug 2013 16:39:32 +0200	[thread overview]
Message-ID: <521CBA24.8000703@samsung.com> (raw)
In-Reply-To: <5217E615.9040101@wwwdotorg.org>

On 08/24/2013 12:45 AM, Stephen Warren wrote:
> On 08/23/2013 10:01 AM, Sylwester Nawrocki wrote:
>> > On 08/18/2013 10:14 PM, Sylwester Nawrocki wrote:
>>> >> This patch enables the JPEG codec on S5PV210 and Exynos4210 SoCs. There are
>>> >> some differences in newer versions of the JPEG codec IP on SoCs like Exynos4x12
>>> >> and Exynos5 series and support for them will be added in subsequent patches.
>>> >>
>>> >> Cc: Andrzej Pietrasiewicz <andrzej.p@samsung.com>
>>> >> Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
>> > 
>> > Could a DT maintainer review/Ack the binding in this patch ?
>
> The binding looks reasonable to me, so,
> Acked-by: Stephen Warren <swarren@nvidia.com>

Thanks Stephen, I've queued this for v3.13.

--
Regards,
Sylwester

      reply	other threads:[~2013-08-27 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-18 20:14 [PATCH] s5p-jpeg: Add initial device tree support for S5PV210/Exynos4210 SoCs Sylwester Nawrocki
2013-08-23 16:01 ` Sylwester Nawrocki
2013-08-23 22:45   ` Stephen Warren
2013-08-27 14:39     ` Sylwester Nawrocki [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=521CBA24.8000703@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=Mark.Rutland@arm.com \
    --cc=Pawel.Moll@arm.com \
    --cc=andrzej.p@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@wwwdotorg.org \
    --cc=sylvester.nawrocki@gmail.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).