From: Smitha T Murthy <smitha.t@samsung.com>
To: Andrzej Hajda <a.hajda@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
kyungmin.park@samsung.com, kamil@wypas.org, jtp.park@samsung.com,
mchehab@kernel.org, pankaj.dubey@samsung.com, krzk@kernel.org,
m.szyprowski@samsung.com, s.nawrocki@samsung.com
Subject: Re: [Patch v3 04/11] [media] s5p-mfc: Support MFCv10.10 buffer requirements
Date: Mon, 03 Apr 2017 17:41:41 +0530 [thread overview]
Message-ID: <1491221501.8493.97.camel@smitha-fedora> (raw)
In-Reply-To: <598903bd-d798-ecc2-a1cf-4c104a091c2c@samsung.com>
On Mon, 2017-04-03 at 09:41 +0200, Andrzej Hajda wrote:
> On 31.03.2017 11:06, Smitha T Murthy wrote:
> > Aligning the luma_dpb_size, chroma_dpb_size, mv_size and me_buffer_size
> > for MFCv10.10.
> >
> > Signed-off-by: Smitha T Murthy <smitha.t@samsung.com>
>
> Reviewed-by: Andrzej Hajda <a.hajda@samsung.com>
> --
> Regards
> Andrzej
>
>
Thank you for the review.
Regards,
Smitha
next prev parent reply other threads:[~2017-04-03 12:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170331090425epcas1p4de8762ee73be91312a76a73638bac253@epcas1p4.samsung.com>
2017-03-31 9:06 ` [Patch v3 00/11] Add MFC v10.10 support Smitha T Murthy
2017-03-31 9:06 ` [Patch v3 01/11] [media] s5p-mfc: Rename IS_MFCV8 macro Smitha T Murthy
2017-03-31 9:06 ` [Patch v3 02/11] [media] s5p-mfc: Adding initial support for MFC v10.10 Smitha T Murthy
2017-03-31 9:06 ` [Patch v3 03/11] [media] s5p-mfc: Use min scratch buffer size as provided by F/W Smitha T Murthy
2017-03-31 9:06 ` [Patch v3 04/11] [media] s5p-mfc: Support MFCv10.10 buffer requirements Smitha T Murthy
2017-04-03 7:41 ` Andrzej Hajda
2017-04-03 12:11 ` Smitha T Murthy [this message]
2017-03-31 9:06 ` [Patch v3 05/11] [media] videodev2.h: Add v4l2 definition for HEVC Smitha T Murthy
2017-04-03 8:11 ` Hans Verkuil
2017-04-03 12:13 ` Smitha T Murthy
2017-03-31 9:06 ` [Patch v3 06/11] [media] s5p-mfc: Add support for HEVC decoder Smitha T Murthy
2017-04-03 8:13 ` Hans Verkuil
2017-04-03 12:14 ` Smitha T Murthy
2017-03-31 9:06 ` [Patch v3 07/11] Documentation: v4l: Documentation for HEVC v4l2 definition Smitha T Murthy
2017-04-03 8:10 ` Hans Verkuil
2017-04-03 12:12 ` Smitha T Murthy
2017-04-03 12:12 ` Hans Verkuil
2017-04-03 12:20 ` Smitha T Murthy
2017-03-31 9:06 ` [Patch v3 08/11] [media] s5p-mfc: Add VP9 decoder support Smitha T Murthy
2017-03-31 9:06 ` [Patch v3 09/11] [media] v4l2: Add v4l2 control IDs for HEVC encoder Smitha T Murthy
2017-04-03 8:22 ` Hans Verkuil
2017-04-03 12:15 ` Smitha T Murthy
2017-03-31 9:06 ` [Patch v3 10/11] [media] s5p-mfc: Add support " Smitha T Murthy
2017-04-03 8:59 ` Andrzej Hajda
2017-04-03 12:18 ` Smitha T Murthy
2017-03-31 9:06 ` [Patch v3 11/11] Documention: v4l: Documentation for HEVC CIDs Smitha T Murthy
2017-04-03 8:28 ` Hans Verkuil
2017-04-04 10:39 ` Smitha T Murthy
2017-03-31 13:29 ` [Patch v3 00/11] Add MFC v10.10 support Andrzej Hajda
2017-04-03 6:15 ` Smitha T Murthy
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=1491221501.8493.97.camel@smitha-fedora \
--to=smitha.t@samsung.com \
--cc=a.hajda@samsung.com \
--cc=jtp.park@samsung.com \
--cc=kamil@wypas.org \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=pankaj.dubey@samsung.com \
--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