On Fri, Mar 04, 2016 at 05:40:29PM +0100, Daniel Vetter wrote:
> On Thu, Mar 03, 2016 at 08:17:14AM -0800, Greg Kroah-Hartman wrote:
> > On Thu, Mar 03, 2016 at 11:37:17AM -0300, Gustavo Padovan wrote:
> > > From: Gustavo Padovan
> > >
> > > Play safe and add flags member to all structs. So we
Hi Greg,
Allow me to chip in as well.
On 3 March 2016 at 16:17, Greg Kroah-Hartman
wrote:
> On Thu, Mar 03, 2016 at 11:37:17AM -0300, Gustavo Padovan wrote:
>> From: Gustavo Padovan
>>
>> Play safe and add flags member to all structs. So we don't need to
>> break API or create new IOCTL in
On Thu, Mar 03, 2016 at 08:17:14AM -0800, Greg Kroah-Hartman wrote:
> On Thu, Mar 03, 2016 at 11:37:17AM -0300, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Play safe and add flags member to all structs. So we don't need to
> > break API or create new IOCTL in the future if new
On Thu, Mar 03, 2016 at 08:17:14AM -0800, Greg Kroah-Hartman wrote:
> On Thu, Mar 03, 2016 at 11:37:17AM -0300, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Play safe and add flags member to all structs. So we don't need to
> > break API or create new IOCTL in the future if new
On Thu, Mar 3, 2016 at 3:54 PM, Rob Clark wrote:
> On Thu, Mar 3, 2016 at 11:17 AM, Greg Kroah-Hartman
> wrote:
>> On Thu, Mar 03, 2016 at 11:37:17AM -0300, Gustavo Padovan wrote:
>>> From: Gustavo Padovan
>>>
>>> Play safe and add flags member to all structs. So we don't need to
>>> break API
2016-03-03 Gustavo Padovan :
> Hi Greg,
>
> 2016-03-03 Greg Kroah-Hartman :
>
> > On Thu, Mar 03, 2016 at 11:37:17AM -0300, Gustavo Padovan wrote:
> > > From: Gustavo Padovan
> > >
> > > Play safe and add flags member to all structs. So we don't need to
> > > break API or create new IOCTL in
Hi Greg,
2016-03-03 Greg Kroah-Hartman :
> On Thu, Mar 03, 2016 at 11:37:17AM -0300, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Play safe and add flags member to all structs. So we don't need to
> > break API or create new IOCTL in the future if new features that requires
> >
On Thu, Mar 3, 2016 at 11:17 AM, Greg Kroah-Hartman
wrote:
> On Thu, Mar 03, 2016 at 11:37:17AM -0300, Gustavo Padovan wrote:
>> From: Gustavo Padovan
>>
>> Play safe and add flags member to all structs. So we don't need to
>> break API or create new IOCTL in the future if new features that
From: Gustavo Padovan
Play safe and add flags member to all structs. So we don't need to
break API or create new IOCTL in the future if new features that requires
flags arises.
v2: check if flags are valid (zero, in this case)
v3: return -EINVAL if flags are
On Thu, Mar 03, 2016 at 11:37:17AM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> Play safe and add flags member to all structs. So we don't need to
> break API or create new IOCTL in the future if new features that requires
> flags arises.
>
> v2: check if flags are valid (zero, in
From: Gustavo Padovan
Play safe and add flags member to all structs. So we don't need to
break API or create new IOCTL in the future if new features that requires
flags arises.
v2: check if flags are valid (zero, in this case)
v3: return -EINVAL if flags are
11 matches
Mail list logo