[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f48e9219-3092-1b1f-4458-f9437746bf14@xs4all.nl>
Date: Sat, 23 Sep 2017 09:35:31 +0200
From: Hans Verkuil <hverkuil@...all.nl>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>,
linux-media@...r.kernel.org
Cc: Sakari Ailus <sakari.ailus@....fi>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Jan Kara <jack@...e.cz>,
Javier Martinez Canillas <javier@....samsung.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Lorenzo Stoakes <lstoakes@...il.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Michal Hocko <mhocko@...e.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH 0/8] [media] v4l2-core: Fine-tuning for some function
implementations
On 22/09/17 22:08, SF Markus Elfring wrote:
>> Sorry Markus, just stay away from the videobuf-* sources.
>
> Will the software evolution be continued for related source files?
> Are there any update candidates left over in the directory “v4l2-core”?
Sorry, I don't understand the question. We don't want to touch the
videobuf-* files unless there is a very good reason. That old videobuf
framework is deprecated and the code is quite fragile (i.e. easy to break
things).
Everything else in that directory is under continuous development.
It's core code though, so it gets a much more in-depth code review than
patches for e.g. a driver.
Regards,
Hans
Powered by blists - more mailing lists