On Tue, 2018-03-13 at 07:51 +0800, Jun Zhao wrote:
>
> On 2018/3/12 20:47, Mark Thompson wrote:
> > On 12/03/18 00:41, Jun Zhao wrote:
> > > On 2018/3/12 2:30, Mark Thompson wrote:
> > > > Apply the same logic as the previous patch to H.265. There are no cases
> > > > which currently overflow
On 2018/3/12 20:47, Mark Thompson wrote:
> On 12/03/18 00:41, Jun Zhao wrote:
>> On 2018/3/12 2:30, Mark Thompson wrote:
>>> Apply the same logic as the previous patch to H.265. There are no cases
>>> which currently overflow here, but this is still more consistent.
>>> ---
>>>
On 12/03/18 00:41, Jun Zhao wrote:
> On 2018/3/12 2:30, Mark Thompson wrote:
>> Apply the same logic as the previous patch to H.265. There are no cases
>> which currently overflow here, but this is still more consistent.
>> ---
>> libavcodec/cbs_h265_syntax_template.c | 16
>> 1
On 2018/3/12 2:30, Mark Thompson wrote:
> Apply the same logic as the previous patch to H.265. There are no cases
> which currently overflow here, but this is still more consistent.
> ---
> libavcodec/cbs_h265_syntax_template.c | 16
> 1 file changed, 8 insertions(+), 8
Apply the same logic as the previous patch to H.265. There are no cases
which currently overflow here, but this is still more consistent.
---
libavcodec/cbs_h265_syntax_template.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git
