From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on archive.lwn.net X-Spam-Level: X-Spam-Status: No, score=-5.6 required=5.0 tests=DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by archive.lwn.net (Postfix) with ESMTP id 44FD27D062 for ; Sun, 24 Jun 2018 23:41:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751966AbeFXXlm (ORCPT ); Sun, 24 Jun 2018 19:41:42 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:39773 "EHLO out2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751965AbeFXXll (ORCPT ); Sun, 24 Jun 2018 19:41:41 -0400 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 7AFBF215F2; Sun, 24 Jun 2018 19:41:40 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sun, 24 Jun 2018 19:41:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tobin.cc; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=W6uR+qNMvQobCppSwLAXhy27OjbPDKywgdajfoxXNuQ=; b=Dgcisf/Y 9IdqeLYyPXtlsrom4HEnuuvkAw0xGISNcVaJxotp8IfBvjfvJ7ILuWIcY6YZ4POz P/9j3hGvQ1DNMSouVkDMaw0ZVlHDbWXKzbtyPTJm3tZwGCQ1cJlaL+4au9TXw/ll +btQFPPlyhUVAJyuOCMjnsu/q1nwqj+WY2G4DtrNpORj+FiDZ9oAzbt15fGT9/ml RrBlffskFPtwE6ZBkRgFytE3OqO4Y/LAoj+dnyrDIBV4aMQTBRGj6JZOTY2JgK/G owdEjPg5dPz3XlxKSfy/mA7HEOClPqJ0eRDZF9AxT9ucaFgXLkM2BhLtVgGM8df2 0e3854ByHO4p7Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=W6uR+qNMvQobCppSwLAXhy27OjbPD KywgdajfoxXNuQ=; b=uLYFh0Smh14wLzF28tKnzPJtJ5076mKHtWzEj0+bhlHt4 +Vnsg6XMhvIA9fbjM3d/FJXwfYFoBiDrRu4w/HbrXE3Ly03UtdgrENtOBEIyYnfv A34jmX6HRI2jukGAvaqioa4jqUfsVcZyiqvcuEtELkSOcNdP3+XsQJ9aD6mk/Bim JEmubZZui83tStNwCurgiF151sZ5NobjlBhz538NMPjey0i9svAB0hbJ/Yl0SDBw ijOQGMnSREYv1pRXHF/LkRe37Cz+YgS/wznRPgRip9gC6/q+RtMf6izuspgy77zy sS4JO7EG8Sm273CjDCo+OJOLuUXSFtdKzN10l36bw== X-ME-Proxy: X-ME-Sender: Received: from localhost (ppp121-44-217-101.bras1.syd2.internode.on.net [121.44.217.101]) by mail.messagingengine.com (Postfix) with ESMTPA id 986D1E4648; Sun, 24 Jun 2018 19:41:39 -0400 (EDT) Date: Mon, 25 Jun 2018 09:41:35 +1000 From: "Tobin C. Harding" To: Randy Dunlap Cc: Jonathan Corbet , Jeff Kirsher , "David S. Miller" , linux-doc@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/4] docs: e100[0] fix build errors Message-ID: <20180624234135.GE3006@eros> References: <20180622003708.31848-1-me@tobin.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Mailer: Mutt 1.9.4 (2018-02-28) User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On Fri, Jun 22, 2018 at 01:22:37PM -0700, Randy Dunlap wrote: > Hi Tobin, > > On 06/21/2018 05:37 PM, Tobin C. Harding wrote: > > Hi Jonathan, > > > > This patch set fixes current docs build failure on Linus' mainline > > > > commit: (ba4dbdedd3ed Merge tag 'jfs-4.18' of git://github.com/kleikamp/linux-shaggy) > > > > (FYI this is 8 commits after Linux 4.18-rc1). > > > > And also same build errors on today's linux-next > > > > 8439c34f07a3 (tag: next-20180621, linux-next/master, linux-next) Add linux-next specific files for 20180621 > > > > > > I split the patches in between the two drivers to enable use of the > > 'Fixes:' tag. > > > > Tobin C. Harding (4): > > Documentation: e100: Use correct heading adornment > > Documentation: e1000: Use correct heading adornment > > Documentation: e100: Fix docs build error > > Documentation: e1000: Fix docs build error > > > > Documentation/networking/e100.rst | 112 +++++++++++++++-------------- > > Documentation/networking/e1000.rst | 76 ++++++++++---------- > > 2 files changed, 96 insertions(+), 92 deletions(-) > > I am still seeing a few warnings (your 4 patches applied to > linux-next-20180622): > > linux-next-20180622/Documentation/networking/e100.rst:57: WARNING: Literal block expected; none found. > linux-next-20180622/Documentation/networking/e100.rst:68: WARNING: Literal block expected; none found. > linux-next-20180622/Documentation/networking/e100.rst:75: WARNING: Literal block expected; none found. > linux-next-20180622/Documentation/networking/e100.rst:84: WARNING: Literal block expected; none found. > linux-next-20180622/Documentation/networking/e100.rst:93: WARNING: Inline emphasis start-string without end-string. > linux-next-20180622/Documentation/networking/e1000.rst:83: ERROR: Unexpected indentation. > linux-next-20180622/Documentation/networking/e1000.rst:84: WARNING: Block quote ends without a blank line; unexpected unindent. > linux-next-20180622/Documentation/networking/e1000.rst:173: WARNING: Definition list ends without a blank line; unexpected unindent. > linux-next-20180622/Documentation/networking/e1000.rst:236: WARNING: Definition list ends without a blank line; unexpected unindent. > > > You didn't get these warnings? or they weren't important? > or "perfect" was not your primary goal? :) [which is fine] > > [I see around 50 similar doc formatting warnings/errors in the entire > Documentation build.] Thanks for testing this Randy. You are right there are a bunch of warnings, I did not think to grep for warnings on these files - sloppy work by me. The series has been applied already but I'll add clearing these warnings to my TODO list. > Anyway, much better than it was. Thanks. > > Tested-by: Randy Dunlap Thanks again, Tobin. -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html