From: Tomasz Figa <tomasz.figa@gmail.com>
To: Arun Kumar K <arun.kk@samsung.com>,
linux-media@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Cc: k.debski@samsung.com, s.nawrocki@samsung.com,
posciak@chromium.org, avnd.kiran@samsung.com,
arunkk.samsung@gmail.com
Subject: Re: [PATCH 0/3] Support for multiple MFC FW sub-versions
Date: Tue, 20 May 2014 20:03:17 +0200 [thread overview]
Message-ID: <537B98E5.6000505@gmail.com> (raw)
In-Reply-To: <1400581029-3475-1-git-send-email-arun.kk@samsung.com>
Hi Arun,
On 20.05.2014 12:17, Arun Kumar K wrote:
> This patchset is for supporting multple firmware sub-versions
> for MFC. Newer firmwares come with changed interfaces and fixes
> without any change in the fw version number.
> So this implementation is as per Tomasz Figa's suggestion [1].
> [1] http://permalink.gmane.org/gmane.linux.kernel.samsung-soc/31735
>
> Arun Kumar K (3):
> [media] s5p-mfc: Remove duplicate function s5p_mfc_reload_firmware
> [media] s5p-mfc: Support multiple firmware sub-versions
> [media] s5p-mfc: Add init buffer cmd to MFCV6
>
> drivers/media/platform/s5p-mfc/s5p_mfc.c | 11 +++---
> drivers/media/platform/s5p-mfc/s5p_mfc_common.h | 11 +++++-
> drivers/media/platform/s5p-mfc/s5p_mfc_ctrl.c | 44 ++++++-----------------
> drivers/media/platform/s5p-mfc/s5p_mfc_opr_v6.c | 6 ++--
> 4 files changed, 30 insertions(+), 42 deletions(-)
>
The whole series looks good.
Reviewed-by: Tomasz Figa <t.figa@samsung.com>
Best regards,
Tomasz
prev parent reply other threads:[~2014-05-20 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 10:17 [PATCH 0/3] Support for multiple MFC FW sub-versions Arun Kumar K
2014-05-20 10:17 ` [PATCH 1/3] [media] s5p-mfc: Remove duplicate function s5p_mfc_reload_firmware Arun Kumar K
2014-05-20 10:17 ` [PATCH 2/3] [media] s5p-mfc: Support multiple firmware sub-versions Arun Kumar K
2014-05-20 11:45 ` Sachin Kamat
2014-05-21 9:15 ` Arun Kumar K
2014-05-20 10:17 ` [PATCH 3/3] [media] s5p-mfc: Add init buffer cmd to MFCV6 Arun Kumar K
2014-05-20 18:03 ` Tomasz Figa [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=537B98E5.6000505@gmail.com \
--to=tomasz.figa@gmail.com \
--cc=arun.kk@samsung.com \
--cc=arunkk.samsung@gmail.com \
--cc=avnd.kiran@samsung.com \
--cc=k.debski@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=posciak@chromium.org \
--cc=s.nawrocki@samsung.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).