Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp1018338ybi; Fri, 14 Jun 2019 07:16:16 -0700 (PDT) X-Google-Smtp-Source: APXvYqzgBEW0Pc5fFYncW1VD+Dn57R40rejNTVA7v4PkrLjQskLkH/kf890V2kQJQ0CA2f8Sbn7T X-Received: by 2002:a17:902:165:: with SMTP id 92mr66601919plb.197.1560521776191; Fri, 14 Jun 2019 07:16:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560521776; cv=none; d=google.com; s=arc-20160816; b=R+A3L4ydQf2MKqNV+KxngWXtWF5S7iIxX60Q+H8+e4bZNVGPBp72mHPawTgaePRKjP QMFS3kp2uLgmY+TMBWHHbHxXFjJTklsPbqocUeTZoRv0nWlT54q7aVcXmb7e0ylWukZa hSGhGvF7xH4R9nIvQ1XjiBY9zJdmKo5nCLNceCqEiCP8LRt22cSybjSeQLZ0+hiGIfjJ 1BHK36FHEtaMxdk/doZLMm6BChtlppxE6p6jlQYkr6phb8p+k7E7/4TAHTK0NMLhpnwE XmCoczGt5wY8T+JHKOq8QO0sXBYb4BUA0UFk2pvTJqBKJjAm4/fOWhCXKsWRGxQxwts8 Ynww== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=pb+N4BqimH++MxT0vxau8qquDEa2CdEMD4rqemuDyzA=; b=wd7qMrBxJYNt0rGGvQ2QHpDs0hMnc9Zc7DSXwMq8NwVyXmtxKZkaXmI+ZLNu4megv5 i/QT+C6ruAvKHGll3PiH6awFMg+JUw/UrIfFUqg0v22fNODLAcC3VW5tXBk1qPSh0sy9 COoM82y8w0tl3v7cZ1hY27jcFEgYjL4gyqkFigRfaeUUszwag3TUMDNjAcVyJxrsBz5d bM5xey7CyCfm2KV3yYZrjmxy+MPrbAjZ3A9j47hMUqPlo3FaCF5qC5tZoKPc0//FsH0+ wsN8pAFvNSFeYrFA1dH8EXUF6CB4TbKLeHOfvW+8SylDjT57vFOC0IwQ1EAJnRxE2ZPA PfuQ== ARC-Authentication-Results: i=1; mx.google.com; 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 q19si2394128pjp.24.2019.06.14.07.15.58; Fri, 14 Jun 2019 07:16:16 -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; 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 S1728894AbfFNOOi (ORCPT + 99 others); Fri, 14 Jun 2019 10:14:38 -0400 Received: from ms.lwn.net ([45.79.88.28]:52178 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728239AbfFNOOi (ORCPT ); Fri, 14 Jun 2019 10:14:38 -0400 Received: from lwn.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 2EACC2D6; Fri, 14 Jun 2019 14:14:37 +0000 (UTC) Date: Fri, 14 Jun 2019 08:14:36 -0600 From: Jonathan Corbet To: Jani Nikula Cc: Greg Kroah-Hartman , Mauro Carvalho Chehab , Linux Doc Mailing List , Mauro Carvalho Chehab , Mauro Carvalho Chehab , linux-kernel@vger.kernel.org Subject: Re: [PATCH 05/14] scripts: add an script to parse the ABI files Message-ID: <20190614081436.3f41746b@lwn.net> In-Reply-To: <87lfy4uuzs.fsf@intel.com> References: <196fb3c497546f923bf5d156c3fddbe74a4913bc.1560477540.git.mchehab+samsung@kernel.org> <87r27wuwc3.fsf@intel.com> <20190614133933.GA1076@kroah.com> <87lfy4uuzs.fsf@intel.com> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 14 Jun 2019 17:00:55 +0300 Jani Nikula wrote: > On Fri, 14 Jun 2019, Greg Kroah-Hartman wrote: > > On Fri, Jun 14, 2019 at 04:31:56PM +0300, Jani Nikula wrote: > >> On Thu, 13 Jun 2019, Mauro Carvalho Chehab wrote: > >> > From: Mauro Carvalho Chehab > >> > > >> > Add a script to parse the Documentation/ABI files and produce > >> > an output with all entries inside an ABI (sub)directory. > >> > > >> > Right now, it outputs its contents on ReST format. It shouldn't > >> > be hard to make it produce other kind of outputs, since the ABI > >> > file parser is implemented in separate than the output generator. > >> > >> Hum, or just convert the ABI files to rst directly. > > > > And what would that look like? > > That pretty much depends on the requirements we want to set on both the > ABI source files and the generated output. Obviously the requirements > can be conflicting; might be hard to produce fancy output if the input > is very limited. The real question, I guess, is: is there anything else that depends on the current format of those files? That could make reformatting them harder. Otherwise it seems like Jani's fieldlist idea might have some potential. We could consider a *really* simple preprocessing step if we really wanted ("prepend a colon on relevant lines and join with the following line if need be") to keep the current format nearly unchanged. jon