From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id B6066A055A; Tue, 25 Feb 2020 17:59:16 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8CE6E1BF8D; Tue, 25 Feb 2020 17:59:15 +0100 (CET) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id AB7691BC24 for ; Tue, 25 Feb 2020 17:59:13 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 36C292211A; Tue, 25 Feb 2020 11:59:12 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 25 Feb 2020 11:59:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=jqLYnVXTVo+iZfE+C738vC6t65ZvEz6xVVkBKeJGq8M=; b=lnmDtSImL856 bCqykn4orkqJv8FQvfU5cnfo75nbVSwkodfxyHG+cLinod9VtUeC2837KC2V9I4o 5Md54Vo6ulVlH5BQciMDY1gx0S7VzvNr3mP8ZdE67EuqpmWs06vpQAumF1BDrhQ9 nPgD12IE1ku0FNQXCjOoVxfXPMIZIwo= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=jqLYnVXTVo+iZfE+C738vC6t65ZvEz6xVVkBKeJGq 8M=; b=li4UNJG7omHLWy3RVq7BOkZteJwCJq0rCbjdBbOa/evA2aSp+jpNSsEjk 0yYwhClzGnAhi/y8JghSSqXNd4596Vzv6XFPaA+mvjT5nRSpZb9CYYjZP1IGWhIi 5ssGLVPRFnA4cSf7uzhYZo17UfkyP3CPQIcIFv5eWigeIRQ2evG2cUZRFEraoi+v +XSoY3sbEv/54bO4b7DykIPFGvQKTlNuwjhI11CKQPuurXTn5ny+pKYLpkQZgck3 MKLZO+pVMhV3lr5UpWWRY1SMnA9Eeab1+PZJCtnnXUPsTFq0yYNzgYiyaZKZHqSe KAhk/pdX8mIx37nmsCmzz3+ln+Ubw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrledvgdelgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucffoh hmrghinhepshhouhhrtggvfhhorhhgvgdrihhonecukfhppeejjedrudefgedrvddtfedr udekgeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 05D7030610E8; Tue, 25 Feb 2020 11:59:10 -0500 (EST) From: Thomas Monjalon To: David Hunt , Ferruh Yigit , john.mcnamara@intel.com, Bernard Iremonger Cc: dev@dpdk.org, David Marchand , Bruce Richardson Date: Tue, 25 Feb 2020 17:59:09 +0100 Message-ID: <2915716.TQGk6oTFT5@xps> In-Reply-To: References: <20200107091343.22965-1-david.hunt@intel.com> <20200217104817.23401-1-david.hunt@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2] doc: rework vm power manager user guide X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 25/02/2020 17:46, Ferruh Yigit: > On 2/17/2020 10:48 AM, David Hunt wrote: > > Review and re-work of vm_power_manager documentation. Hopefully this > > is clearer, easier to follow. > > > > Signed-off-by: David Hunt > <...> > > Bernard reported following errors [1] in DPDK 20.02-rc4 caused by this patch, > while building the docs in Ubuntu with "Sphinx (sphinx-build) 1.3.6". > > I can't reproduce it with "sphinx-build 1.8.5" on Ubuntu, or with "sphinx-build > 2.3.1" on Fedora. > > I am putting this as a record, not sure if something needs to be done. > > @John, do we have a minimum required sphinx version required? > > > > [1] > .../doc/guides/sample_app_ug/vm_power_management.rst:420: ERROR: Malformed table. > Column span alignment problem in table line 5. > > .../doc/guides/sample_app_ug/vm_power_management.rst:545: ERROR: Malformed table. > Column span alignment problem in table line 5. > > .../doc/guides/sample_app_ug/vm_power_management.rst:754: ERROR: Malformed table. > Column span alignment problem in table line 5. Thank you for reporting. I was testing PDF on the server at the same time and discovered this issue. We should avoid big tables. Here the table have only two columns so they can be formatted differently. One option is to use the definition lists: https://docutils.sourceforge.io/docs/user/rst/quickref.html#definition-lists Please could we have a fix very quickly? It is a blocker for the release (planned to be done in the next hour).