Hello Mauro,
On 12/28/2015 11:03 AM, Mauro Carvalho Chehab wrote:
> There are a few discussions left with regards to this ioctl:
>
> 1) the name of the new structs will contain _v2_ on it?
> 2) what's the best alternative to avoid compat32 issues?
>
> Due to that, let's postpone the addition of
There are a few discussions left with regards to this ioctl:
1) the name of the new structs will contain _v2_ on it?
2) what's the best alternative to avoid compat32 issues?
Due to that, let's postpone the addition of this new ioctl to
the next Kernel version, to give people more time to discuss
On Mon, Dec 28, 2015 at 08:37:19AM -0700, Shuah Khan wrote:
> On 12/28/2015 07:03 AM, Mauro Carvalho Chehab wrote:
> > There are a few discussions left with regards to this ioctl:
> >
> > 1) the name of the new structs will contain _v2_ on it?
> > 2) what's the best alternative to avoid compat32
On 12/28/2015 08:44 AM, Greg KH wrote:
> On Mon, Dec 28, 2015 at 08:37:19AM -0700, Shuah Khan wrote:
>> On 12/28/2015 07:03 AM, Mauro Carvalho Chehab wrote:
>>> There are a few discussions left with regards to this ioctl:
>>>
>>> 1) the name of the new structs will contain _v2_ on it?
>>> 2)
On 12/28/2015 07:03 AM, Mauro Carvalho Chehab wrote:
> There are a few discussions left with regards to this ioctl:
>
> 1) the name of the new structs will contain _v2_ on it?
> 2) what's the best alternative to avoid compat32 issues?
>
> Due to that, let's postpone the addition of this new
