[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200228113911.GA121952@google.com>
Date: Fri, 28 Feb 2020 20:39:11 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Hans Verkuil <hverkuil@...all.nl>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>,
Hans Verkuil <hans.verkuil@...co.com>,
Tomasz Figa <tfiga@...omium.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Kyungmin Park <kyungmin.park@...sung.com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Sakari Ailus <sakari.ailus@....fi>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Pawel Osciak <posciak@...omium.org>,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv3 05/11] videobuf2: handle
V4L2_FLAG_MEMORY_NON_CONSISTENT flag
On (20/02/28 09:50), Hans Verkuil wrote:
> On 2/28/20 4:57 AM, Sergey Senozhatsky wrote:
> > On (20/02/27 13:36), Hans Verkuil wrote:
> > [..]
[..]
> >>> + * - __u32
> >>> + - ``reserved``\ [6]
> >>> - A place holder for future extensions. Drivers and applications
> >>> must set the array to zero.
> >>
> >> Old drivers and applications still think reserved is [7] and will zero this.
> >
> > Just to make sure, does this mean that you also want me to drop the
> > "Drivers and applications must set the array to zero" sentence?
>
> Not for the reserved field, only for the flags field.
Got it.
So V4 is ready. Do you think it'll make sense to send it
out now or next week?
-ss
Powered by blists - more mailing lists