From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from osg.samsung.com ([64.30.133.232]:40743 "EHLO osg.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753892AbdLSPey (ORCPT ); Tue, 19 Dec 2017 10:34:54 -0500 Date: Tue, 19 Dec 2017 13:34:46 -0200 From: Mauro Carvalho Chehab To: Laurent Pinchart Cc: Sakari Ailus , Linux Media Mailing List , Mauro Carvalho Chehab , Hans Verkuil , Laurent Pinchart , Sakari Ailus , Marek Szyprowski , Tomasz Figa , Ramesh Shanmugasundaram , Ricardo Ribalda Delgado Subject: Re: [PATCH 2/8] media: v4l2-ioctl.h: convert debug into an enum of bits Message-ID: <20171219133446.3b42ad19@vento.lan> In-Reply-To: <1829332.DyU8Vvd1sp@avalon> References: <20171219113927.i2srypzhigkijetf@valkosipuli.retiisi.org.uk> <1615432.c1z8s9p1mm@avalon> <1829332.DyU8Vvd1sp@avalon> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-media-owner@vger.kernel.org List-ID: Em Tue, 19 Dec 2017 16:05:46 +0200 Laurent Pinchart escreveu: > On Tuesday, 19 December 2017 16:02:02 EET Laurent Pinchart wrote: > > On Tuesday, 19 December 2017 13:39:27 EET Sakari Ailus wrote: > > > Hi Mauro, > > > > > > On Mon, Dec 18, 2017 at 05:53:56PM -0200, Mauro Carvalho Chehab wrote: > > > > The V4L2_DEV_DEBUG_IOCTL macros actually define a bitmask, > > > > but without using Kernel's modern standards. Also, > > > > documentation looks akward. > > > > > > > > So, convert them into an enum with valid bits, adding > > > > the correspoinding kernel-doc documentation for it. > > > > > > The pattern of using bits for flags is a well established one and I > > > wouldn't deviate from that by requiring the use of the BIT() macro. There > > > are no benefits that I can see from here but the approach brings > > > additional > > > risks: misuse of the flags and mimicing the same risky pattern. > > > > > > I'd also like to echo Laurent's concern that code is being changed in odd > > > ways and not for itself, but due to deficiencies in documentation tools. > > > > > > I believe the tooling has to be improved to address this properly. That > > > only needs to done once, compared to changing all flag definitions to > > > enums. > > > > That's my main concern too. We really must not sacrifice code readability or > > writing ease in order to work around limitations of the documentation > > system. For this reason I'm strongly opposed to patches 2 and 5 in this > > series. > > And I forgot to mention patch 8/8. Let's drop those three and improve the > documentation system instead. Are you volunteering yourself to write the kernel-doc patches? :-) Thanks, Mauro