Em Fri, 23 Mar 2018 17:31:53 +0200
Sakari Ailus escreveu:
> On Fri, Mar 23, 2018 at 11:08:55AM -0300, Mauro Carvalho Chehab wrote:
> > Em Fri, 23 Mar 2018 11:07:42 -0300
> > Mauro Carvalho Chehab escreveu:
> >
> > > Em Fri, 23 Mar 2018 15:48:41 +0200
> > > Sakari Ailus escreveu:
> > >
> >
On Fri, Mar 23, 2018 at 11:08:55AM -0300, Mauro Carvalho Chehab wrote:
> Em Fri, 23 Mar 2018 11:07:42 -0300
> Mauro Carvalho Chehab escreveu:
>
> > Em Fri, 23 Mar 2018 15:48:41 +0200
> > Sakari Ailus escreveu:
> >
> > > An older version of the driver patches were merged accidentally which
> > >
Em Fri, 23 Mar 2018 11:07:42 -0300
Mauro Carvalho Chehab escreveu:
> Em Fri, 23 Mar 2018 15:48:41 +0200
> Sakari Ailus escreveu:
>
> > An older version of the driver patches were merged accidentally which
> > resulted in missing the array_size parameter that tells the length of the
> > array th
Em Fri, 23 Mar 2018 15:48:41 +0200
Sakari Ailus escreveu:
> An older version of the driver patches were merged accidentally which
> resulted in missing the array_size parameter that tells the length of the
> array that contains the different supported sizes.
>
> Bring it back to v4l2_find_neares
An older version of the driver patches were merged accidentally which
resulted in missing the array_size parameter that tells the length of the
array that contains the different supported sizes.
Bring it back to v4l2_find_nearest size and make the corresponding change
for the drivers using it as w
