From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751465AbdIWP1v (ORCPT <rfc822;w@1wt.eu>);
        Sat, 23 Sep 2017 11:27:51 -0400
Received: from mout.web.de ([212.227.17.12]:62416 "EHLO mout.web.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1750778AbdIWP1t (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Sat, 23 Sep 2017 11:27:49 -0400
Subject: Re: [media] v4l2-core: Fine-tuning for some function implementations
To: Hans Verkuil <hverkuil@xs4all.nl>, linux-media@vger.kernel.org
Cc: Sakari Ailus <sakari.ailus@iki.fi>,
        Dave Hansen <dave.hansen@linux.intel.com>, Jan Kara <jack@suse.cz>,
        Javier Martinez Canillas <javier@osg.samsung.com>,
        "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
        Lorenzo Stoakes <lstoakes@gmail.com>,
        Mauro Carvalho Chehab <mchehab@kernel.org>,
        Michal Hocko <mhocko@suse.com>, LKML <linux-kernel@vger.kernel.org>,
        kernel-janitors@vger.kernel.org
References: <9268b60d-08ba-c64e-1848-f84679d64f80@users.sourceforge.net>
 <20161227115111.GN16630@valkosipuli.retiisi.org.uk>
 <b804f4dd-392e-ae8e-41de-a02260fef550@xs4all.nl>
 <8241c145-03f4-6dd2-401e-7d251cd5d251@users.sourceforge.net>
 <f48e9219-3092-1b1f-4458-f9437746bf14@xs4all.nl>
From: SF Markus Elfring <elfring@users.sourceforge.net>
Message-ID: <85cf0892-68d4-560e-58df-874148d82143@users.sourceforge.net>
Date: Sat, 23 Sep 2017 17:27:10 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <f48e9219-3092-1b1f-4458-f9437746bf14@xs4all.nl>
Content-Type: text/plain; charset=windows-1252
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:hWd6K1qKTxaZlzS7rcycVzSXKh7TBas2e8wVUHcWN4qDswoTm/l
 RzfgkJdKf93P4+X/yHWORJ72w6WOu9xlP0CXCljzXArcKEb1unCJKTiVsEw9QsW/U6H5YXZ
 LKFwzDMUWw0PXIT1rgQg3+mBS2jdKQVZiHdzHyg191Z/hm05xemca7vliiGI8GY65m4QU6A
 1hGJMWBrZXJavGsMvuAbA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:qRQwQJ/vSvw=:n2iSvSTXHwGYXLju3poJnY
 0hI7ZktSXCTSr85viBN+8ZqQqiJwJE1qHPy/6b0pvjAJSyqVnGZz0N+0QFsJAjIBdsDDI4VBm
 7wHKcSgDiq/YUzD7/QzKENrsGlHsXzVzpTdDPjNS5KMd6g5KjRUWzUVep9JtYmaouz5xJER3v
 pKW9ndD8bA2mEQFvYIgkmwBKytMxh/0OvNXmV5OeCjVd3H10iJ4eimPBtq/359ri3Bth8YHnX
 lXTAvSxK0hMvAFNNOd3oCn9lLNX683DUO+9lVqlxol+/P4+kUUQOfpgwFgkz9DcuJpiUmlJKh
 be2biMByLwqRodi7omsYHjSdD6eTYuasUJg3ROzit5YGrvUZ0L2van6d1214BN2ywYPBAmc3c
 II9hG/wL8cYzuxQMgWKkd5bqE6NKfiPoIU50lpObNIFw4yqNZP75acl+BzF3xNSCAM7FXcCUF
 MuDfeXJSAojePoIs2yRH4014K32WviamchAixw3J49Vfe1Invwnebn2XdUxGRXS7t5+F/z9wo
 js/vOnl/DodbxOJCJuQIfPcVsJPoDNdvLgG9TGaLqYq78zwDtcu4IQpFbuYQw65pctm+K5nz2
 GaXrotvnfgAn3luNbV1KnPOFgaz2jIgNYX4fGotXbthulLqjmVHlL7dk1gzTLYys5DGzjjO3O
 tpKTlbBmk8+bFzCc0bEH2A7gcJwNRuMY/URXbfJv+5kM54EuSYygp3s7aR5MkYYZU+SExPYJd
 fcCgrCQH+KtFfri3pM9HvMXwlJIOx1xs5hLP9k+PuR+NF69Ur1dLCrGYPNwqfMgkmbpZvNPgz
 lONUuOf45mpL9rgqcyfn8t6ya8h5tGpr/sy0ZSx+J6FhexBDyQ=
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

>> 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.

I try to explain my view again.


> We don't want to touch the videobuf-* files unless there is a very good reason.

I hoped that my update suggestions could be good enough once more for this area.


> That old videobuf framework is deprecated and the code is quite fragile
> (i.e. easy to break things).

How do you think about to move this stuff into a separate subdirectory
so that it might become a bit easier to distinguish these software components?


> Everything else in that directory is under continuous development.

I am curious if there are still update candidates left over
(also from my selection of change possibilities).

Regards,
Markus