Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp2210066ybi; Thu, 20 Jun 2019 10:55:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqxoqP7ueI8zE/LNvURJMd6nRv6dVwv320Iq/I37MeI33wBVAth4zAoSIg0GSx7DBJT+AViX X-Received: by 2002:a63:3d09:: with SMTP id k9mr8281028pga.321.1561053336296; Thu, 20 Jun 2019 10:55:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561053336; cv=none; d=google.com; s=arc-20160816; b=IglDsJUD5pEKaW9YCC7fL+Ggl4fpWAS3tlURvjp7hYe3cGDDAz+8SWHpSb4Eb44F4M 4DqstEUMbcmLPT7NQvj/pSiW3377oaKs3/mOgmhaECMx9VDQffrJHm1HJlPGZ+pQce7n W5E1pfawXmpzaBZdopnvWJpYGR3naxdO1dYJhCHXgz1SUDBtutTOQUE2JhytrN72PMCd /dvVYjKrDlzI7/1ET414V7hQ7qzjHcWOh4x60cWs/PpqZJjHhx9jY6kOZeqQM3zjuKEI 4gc2wXQ2XpxVe4l2CY0+qM8fl174k/F8MuuzChFRJ8M4beN+vIbyi2OGMD6/vNdLFHiX +1Mw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=W9tWT3L+BSAxIdpLH0WF+CcCBfyJFLYpcPLslIavXGM=; b=mD0flSIX5DsRF3rdwZk/5H5sr2EUJz1CV4OMIwRd9FlcN1totihXuAlZL9ayXbJs40 y0IZvDKYRTLUGYXfzwQ7p/JMuqGds9EsSKsezcq1onhtT/7e1NaDPNYTNL2MGyFHN8Jz q2f+LLSLqJKYiPtdJs/6XPNm8OJc4ByA36Z7flEuWVbAvcEIuvGboNeFxpdXUSIFcR6n huBMuYmIrrP4lRSO6e56uvffK3PkG5BcPYLlTB/i6ZIut53gspbltWhHsXEgkgXT5dp2 VJdQxiZF4IOsfGLp5rJaOTQLK8qplJM3dlt5usk6FHHmf3nWXJCpJq1MG0AW5BpnI2RJ Qk1Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Wy2ZF58G; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z14si390009pju.64.2019.06.20.10.55.20; Thu, 20 Jun 2019 10:55:36 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Wy2ZF58G; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726697AbfFTRzP (ORCPT + 99 others); Thu, 20 Jun 2019 13:55:15 -0400 Received: from mail.kernel.org ([198.145.29.99]:43992 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726523AbfFTRzP (ORCPT ); Thu, 20 Jun 2019 13:55:15 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 777222053B; Thu, 20 Jun 2019 17:55:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1561053314; bh=Q0HE6hDJzQ2OikJgpyS6TE3/enHYzxs952B1kdtn/ho=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Wy2ZF58GPPc+bi2mWXQOYlZdF0/LNldMRGpOxlArsrqWnFtpyMUg0tCi+ai7yScUz P7ouUzRAj8NZD+Znjge3Ov8WpqSl/+uIdIA5otte6kFiK3GqpbI+zqYFPFjzkHQeMw sL1hk0+mjyLBQTtYpHQJuXLQbzBMnq34RKQpbwX0= Date: Thu, 20 Jun 2019 19:55:11 +0200 From: Greg Kroah-Hartman To: Mauro Carvalho Chehab Cc: Johan Hovold , Linux Doc Mailing List , Mauro Carvalho Chehab , Mauro Carvalho Chehab , linux-kernel@vger.kernel.org, Jonathan Corbet , Stefan Achatz Subject: Re: [PATCH 04/14] ABI: better identificate tables Message-ID: <20190620175511.GA13038@kroah.com> References: <6bc45c0d5d464d25d4d16eceac48a2f407166944.1560477540.git.mchehab+samsung@kernel.org> <20190619125135.GG25248@localhost> <20190619105633.7f7315a5@coco.lan> <20190619150207.GA19346@kroah.com> <20190620120150.GH6241@localhost> <20190620125413.GA5170@kroah.com> <20190620112034.0d2be447@coco.lan> <20190620162945.GC23052@kroah.com> <20190620141628.71157dda@coco.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190620141628.71157dda@coco.lan> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 20, 2019 at 02:16:28PM -0300, Mauro Carvalho Chehab wrote: > Em Thu, 20 Jun 2019 18:29:45 +0200 > Greg Kroah-Hartman escreveu: > > > On Thu, Jun 20, 2019 at 11:20:34AM -0300, Mauro Carvalho Chehab wrote: > > > Em Thu, 20 Jun 2019 14:54:13 +0200 > > > Greg Kroah-Hartman escreveu: > > > > > > > On Thu, Jun 20, 2019 at 02:01:50PM +0200, Johan Hovold wrote: > > > > > > I don't know when "Description" and "RST-Description" would be used. > > > > > > Why not just parse "Description" like rst text and if things are "messy" > > > > > > we fix them up as found, like you did with the ":" here? It doesn't > > > > > > have to be complex, we can always fix them up after-the-fact if new > > > > > > stuff gets added that doesn't quite parse properly. > > > > > > > > > > > > Just like we do for most kernel-doc formatting :) > > > > > > > > > > But kernel-doc has a documented format, which was sort of the point I > > > > > was trying to make. If the new get_abi.pl scripts expects a colon I > > > > > think it should be mentioned somewhere (e.g. Documentation/ABI/README). > > > > > > > > > > Grepping for attribute entries in linux-next still reveals a number > > > > > descriptions that still lack that colon and use varying formatting. More > > > > > are bound to be added later, but perhaps that's ok depending on what > > > > > you're aiming at here. > > > > > > > > I'm aiming for "good enough" to start with, and then we can work through > > > > the exceptions. > > > > > > > > But given that Mauro hasn't resent the script that does the conversion > > > > of the files, I don't know if that will even matter... {hint} > > > > > > It sounds I missed something... are you expecting a new version? > > > > Yes, the last round of patches didn't have a SPDX header on the script, > > so I couldn't add it to the tree :( > > I could swear I sent you a version with SPDX on it... anyway, I'm > re-sending the hole thing. The SPDX header addition is on a separate > patch. Ah, you didn't cc: me on the whole thread this time, that's why I missed it last time. I sucked it off lkml now, will look at it in the morning. thanks, greg k-h