From: Vikash Garodia <vgarodia@codeaurora.org>
To: Stanimir Varbanov <stanimir.varbanov@linaro.org>
Cc: hverkuil@xs4all.nl, mchehab@kernel.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, acourbot@chromium.org,
linux-media-owner@vger.kernel.org
Subject: Re: [PATCH] venus: vdec: fix decoded data size
Date: Mon, 08 Oct 2018 16:49:09 +0530 [thread overview]
Message-ID: <a0758f3e3c214f8d6659cf85d6fbe67e@codeaurora.org> (raw)
In-Reply-To: <68f15b8b-3121-3412-2ad1-6647e9afc264@linaro.org>
Hi Stanimir,
On 2018-10-05 20:56, Stanimir Varbanov wrote:
> Hi Vikash,
>
> please, increment the version of the patch next time. This one must be
> v2.
>
> On 10/03/2018 02:30 PM, Vikash Garodia wrote:
>> Exisiting code returns the max of the decoded size and buffer size.
>
> s/Exisiting/Existing
>
Posted v2 with above comments.
Thanks,
Vikash
next prev parent reply other threads:[~2018-10-08 11:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 11:30 [PATCH] venus: vdec: fix decoded data size Vikash Garodia
2018-10-03 12:36 ` Stanimir Varbanov
2018-10-05 15:26 ` Stanimir Varbanov
2018-10-08 11:19 ` Vikash Garodia [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-02 7:44 Vikash Garodia
2018-07-02 8:51 ` Alexandre Courbot
2018-07-06 15:12 ` Stanimir Varbanov
2018-07-06 17:09 ` Alexandre Courbot
2018-07-07 12:26 ` Stanimir Varbanov
2018-07-18 11:31 ` Stanimir Varbanov
2018-07-18 13:26 ` Nicolas Dufresne
2018-07-18 14:37 ` Stanimir Varbanov
2018-09-17 10:00 ` Hans Verkuil
2018-09-17 14:30 ` Stanimir Varbanov
2018-09-17 14:32 ` Hans Verkuil
2018-09-19 10:32 ` Alexandre Courbot
2018-09-19 15:02 ` Stanimir Varbanov
2018-09-19 15:53 ` Nicolas Dufresne
2018-09-20 3:02 ` Tomasz Figa
2018-09-25 9:41 ` Stanimir Varbanov
2018-10-02 7:38 ` Stanimir Varbanov
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=a0758f3e3c214f8d6659cf85d6fbe67e@codeaurora.org \
--to=vgarodia@codeaurora.org \
--cc=acourbot@chromium.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media-owner@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=stanimir.varbanov@linaro.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).