Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp2554242ybi; Mon, 17 Jun 2019 06:48:57 -0700 (PDT) X-Google-Smtp-Source: APXvYqwlfLzTAmoCi2oMdvUJhG/RvHoQhqjq/IOtwi0G/ecaAx8vhREVl0NRi6NiPH2HGfkC/hW4 X-Received: by 2002:a17:902:830b:: with SMTP id bd11mr56128628plb.202.1560779337441; Mon, 17 Jun 2019 06:48:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560779337; cv=none; d=google.com; s=arc-20160816; b=eVVQDivpn9Ls7Sm469QfhpPOHsoKF6Hw3BghGQqrFFHoKgGnfq/FjALghkz3YxLFkI AAENTbxmU8ZxcL0DCUX0E081omNySSZGWdBkbo7j2njBQHyWya4x51WGqggrDrQqblu/ YQ2sgjuz78Lj4uyDZ6dFDn4768tgVog4CaHBRfY09NaRMBCm1dfE5+MASFmIAHF6CaDF WsB0w1NA2s5SlCZhvsYR2KO5RKjHiW2y09/kt9qcnTI0Jp9DEBgpfJuqg08kAJQv71AG /Y5LtuiEIivtkX6arow2DQEPUK77vNS06eHLdm02YxXUffxSKDLDwp9kug+MEl1mzERD By6Q== 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=Zkt/KwdKX0g9wp5JrMD5JwhWlKpu7RT0IuNOEGq2y5o=; b=kL+V4lGrdRlHGDR5B92xagubTt1TtkUL3f5YFwpiTjaGXvjqBZvm943qSQ24xojYCM U12k0YVAdIJ7iWhZ6EfluNjNEgM9wHxTE4W1vBFJmKS/Z7iK7XJUWXUzazF/IOz0R5wW NOy74QhHpXiHC3lfohXGTMnUT9wzx5tLTFqE4qSoXYagSUK96Ta8jFEE1x1MMJ1zjY6i tjbGqLX8Vki784KDF9oFc0VenQZrNc+XcL9Fs8AVzrZUl4G4WgRLUldTd9qU5t/5/c6r rJdwbEUmYs06Zv9oKnko6Xz6WsvL2AnqddbB4im/W7eE0gvU2YHVtxnMrPxCIX6BgJ4c nHEw== 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 v16si4209711pjb.91.2019.06.17.06.48.41; Mon, 17 Jun 2019 06:48:57 -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 S1727586AbfFQNsf (ORCPT + 99 others); Mon, 17 Jun 2019 09:48:35 -0400 Received: from ms.lwn.net ([45.79.88.28]:42882 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725995AbfFQNsf (ORCPT ); Mon, 17 Jun 2019 09:48:35 -0400 Received: from localhost.localdomain (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 13F10300; Mon, 17 Jun 2019 13:48:32 +0000 (UTC) Date: Mon, 17 Jun 2019 07:48:29 -0600 From: Jonathan Corbet To: Greg Kroah-Hartman Cc: Jani Nikula , Mauro Carvalho Chehab , Linux Doc Mailing List , Mauro Carvalho Chehab , Mauro Carvalho Chehab , linux-kernel@vger.kernel.org Subject: Re: [PATCH 12/14] doc-rst: add ABI documentation to the admin-guide book Message-ID: <20190617074829.70cbaa48@lwn.net> In-Reply-To: <20190617125438.GA18554@kroah.com> References: <9da2a7f6ff57d9d53dcbb964eb310f7956522870.1560477540.git.mchehab+samsung@kernel.org> <87o930uvur.fsf@intel.com> <20190614140603.GB7234@kroah.com> <20190614122755.1c7b4898@coco.lan> <874l4ov16m.fsf@intel.com> <20190617125438.GA18554@kroah.com> Organization: LWN.net X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) 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 Mon, 17 Jun 2019 14:54:38 +0200 Greg Kroah-Hartman wrote: > > I think it's just sad to see the documentation system slowly drift > > further away from the ideals we had, and towards the old ways we worked > > so hard to fix. > > What are those ideals? > > I thought the goal was to be able to write documentation in a as much > as a normal text file as possible and have automation turn those files > into "pretty" documentation that we can all use. That was indeed one of the goals. Another was to replace the incredible pile of fragile duct tape that the docs build system had become with something more robust, understandable, and maintainable. We did that, to an extent at least, and life is better. Jani worries that we have been regressing toward duct-tape mode, and I suspect he may be right. I'm certainly as guilty as anybody of tossing stuff in because it's expedient right now. It is right to ask whether we should continue in that direction. Can we slow down just a bit on the ABI files? It may be that Mauro's solution is the best one, but I would really like to think a bit about how all this stuff fits together, and life isn't really even giving me time to tie my shoes these days. I don't think that this is screamingly urgent right now. Thanks, jon