Received: by 10.213.65.68 with SMTP id h4csp364868imn; Fri, 6 Apr 2018 01:17:28 -0700 (PDT) X-Google-Smtp-Source: AIpwx48kM1dGCgmIgV9SE8AoAWaEy2FRVsvy0pujeGLMWQcBn0E+IRmUmYEBm22YXWBrvbhRiTW+ X-Received: by 10.98.68.86 with SMTP id r83mr19863458pfa.145.1523002648487; Fri, 06 Apr 2018 01:17:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523002648; cv=none; d=google.com; s=arc-20160816; b=MyLn9w4Oi0OeSWVb8v0z8nsJRh9owa3vyZZhVzeLaZMoWRjGIrsWPMiR3jVGalYe/J +6C1Q9JLaYG2PBJPiORan8ROubwf0rBj1Lwbl3ZMHE/QFO29AnecpM2hoLZSkeHYFgyH fB6a9wLsGogdY/XK19TFyFCZuaiiLqE2PwHKFjSyc2mQBLPTmXbk0Wvj5Yh+EwVXGpf9 aejot/OJCFVn8y+e5d7lWU9H5sOQ8skftg1YZSF8Ub5Rp/d3RoMUH3SoWd7pWbaY2y78 hSucRLpJz6Ng0bDJ3wMTTDVAJxegeaJ+evWdRyx8JjoFoVgQ+cNwMx6b9lgAHhz1OfJY rrMA== 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:arc-authentication-results; bh=8a3lAK/ysqQCBbiKROqnllQcZ/7pFNQwwyeWHCS6coQ=; b=NqKg6jumDVcZFErZrrcnSbf5t161L7i++eWcVZ75FU7Fle/4ohgQabeKfg/HC9Bxhl l2MreJtLO/2JHOctPRaGhQdNLUcYAPp9lw35M3UuBeekbwVLdXn+TpP6LV6H+R/nk90W wfw5/ei+PtTTtW4mliIplN8OzhaABcoIJUeBR/9eqtojVGF/6J/FW8t26Q0mrJXStfSI o7+SgMEQeEJHn6QPGEd7qqXRW0/DdlLl2LoivJOL74vJpzVLGeHbEtTsBSg7zyz8ZfTK vhHoPaqV9zhy0f6N+ikDMOKRi/OeXxR0iI7tZTBZrjw8zXLT8Kark2agj3FM0ZIs4yVY Q7sQ== 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 s21-v6si7408093plr.695.2018.04.06.01.17.14; Fri, 06 Apr 2018 01:17:28 -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 S1751540AbeDFIQC (ORCPT + 99 others); Fri, 6 Apr 2018 04:16:02 -0400 Received: from mga07.intel.com ([134.134.136.100]:25899 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750815AbeDFIQA (ORCPT ); Fri, 6 Apr 2018 04:16:00 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Apr 2018 01:15:59 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,414,1517904000"; d="scan'208";a="44583388" Received: from kuha.fi.intel.com ([10.237.72.189]) by fmsmga001.fm.intel.com with SMTP; 06 Apr 2018 01:15:56 -0700 Received: by kuha.fi.intel.com (sSMTP sendmail emulation); Fri, 06 Apr 2018 11:15:55 +0300 Date: Fri, 6 Apr 2018 11:15:55 +0300 From: Heikki Krogerus To: Greg KH Cc: Masanari Iida , linux-kernel@vger.kernel.org, linux-doc , Jonathan Corbet , linux-usb@vger.kernel.org Subject: Re: make xmldocs failed with error after 4.17 merge period Message-ID: <20180406081555.GB21589@kuha.fi.intel.com> References: <20180406075109.GA21589@kuha.fi.intel.com> <20180406075734.GA16728@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180406075734.GA16728@kroah.com> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 06, 2018 at 09:57:34AM +0200, Greg KH wrote: > On Fri, Apr 06, 2018 at 10:51:09AM +0300, Heikki Krogerus wrote: > > On Fri, Apr 06, 2018 at 12:38:42PM +0900, Masanari Iida wrote: > > > After merge following patch during 4.17 merger period, > > > make xmldocs start to fail with error. > > > > > > [bdecb33af34f79cbfbb656661210f77c8b8b5b5f] > > > usb: typec: API for controlling USB Type-C Multiplexers > > > > > > Error messages. > > > reST markup error: > > > /home/iida/Repo/linux-2.6/Documentation/driver-api/usb/typec.rst:215: > > > (SEVERE/4) Unexpected section title or transition. > > > > > > ------------------------ > > > Documentation/Makefile:93: recipe for target 'xmldocs' failed > > > make[1]: *** [xmldocs] Error 1 > > > Makefile:1527: recipe for target 'xmldocs' failed > > > make: *** [xmldocs] Error 2 > > > > > > $ > > > > > > An ascii graphic in typec.rst cause the error. > > > > Thanks for the report. I'm going to propose that we fix this by > > marking the ascii art as comment: > > > > diff --git a/Documentation/driver-api/usb/typec.rst b/Documentation/driver-api/usb/typec.rst > > index feb31946490b..972c11bf4141 100644 > > --- a/Documentation/driver-api/usb/typec.rst > > +++ b/Documentation/driver-api/usb/typec.rst > > @@ -212,7 +212,7 @@ port drivers can use USB Role Class API with those. > > > > Illustration of the muxes behind a connector that supports an alternate mode: > > > > - ------------------------ > > +.. ------------------------ > > | Connector | > > ------------------------ > > | | > > > > I hope that works. > > Try it and see! :) It will fix this issue. I was just wondering if use of ascii art is acceptable in general with the .rst files? But then again, why wouldn't it be. Sorry for the noise. I'll just send that patch. Thanks, -- heikki