From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] media: s5p-mfc: remove DT hacks and simplify initialization code
Date: Wed, 07 Aug 2013 00:17:36 +0200 [thread overview]
Message-ID: <2081911.Lb2nBczokV@flatron> (raw)
In-Reply-To: <520174F5.6060508@samsung.com>
Hi Kukjin,
On Wednesday 07 of August 2013 07:13:09 Kukjin Kim wrote:
> On 08/06/13 19:22, Kamil Debski wrote:
> > Hi Kukjin,
> >
> > This patch looks good.
> >
> > Best wishes,
> > Kamil Debski
> >
> >> From: Marek Szyprowski [mailto:m.szyprowski at samsung.com]
> >> Sent: Monday, August 05, 2013 2:27 PM
> >>
> >> This patch removes custom initialization of reserved memory regions
> >> from s5p-mfc driver. Memory initialization can be now handled by
> >> generic code.
> >>
> >> Signed-off-by: Marek Szyprowski<m.szyprowski@samsung.com>
> >
> > Acked-by: Kamil Debski<k.debski@samsung.com>
>
> Kamil, thanks for your ack.
>
> Applied.
This is a nice cleanup, but I don't think it should be applied yet,
because it depends on patch 1/2, which needs an Ack from DT maintainers.
Best regards,
Tomasz
next prev parent reply other threads:[~2013-08-06 22:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 12:26 [PATCH 0/2] Exynos: MFC: clean up device tree bindings Marek Szyprowski
2013-08-05 12:26 ` [PATCH 1/2] ARM: Exynos: replace custom MFC reserved memory handling with generic code Marek Szyprowski
2013-08-08 21:00 ` Stephen Warren
2013-08-08 21:19 ` Tomasz Figa
2013-08-08 21:47 ` Stephen Warren
2013-08-08 22:10 ` Tomasz Figa
2013-08-08 22:48 ` Stephen Warren
2013-08-05 12:26 ` [PATCH 2/2] media: s5p-mfc: remove DT hacks and simplify initialization code Marek Szyprowski
2013-08-06 10:22 ` Kamil Debski
2013-08-06 22:13 ` Kukjin Kim
2013-08-06 22:17 ` Tomasz Figa [this message]
2013-08-05 17:12 ` [PATCH 0/2] Exynos: MFC: clean up device tree bindings Kukjin Kim
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=2081911.Lb2nBczokV@flatron \
--to=tomasz.figa@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).