Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp3464961imw; Mon, 11 Jul 2022 09:08:09 -0700 (PDT) X-Google-Smtp-Source: AGRyM1u9i3gwUoLq0uZqdjQkxNk8usXJ7jtYErmJecRojNj0fj80tfOhbZj0ybVsZFibQQYUCM6w X-Received: by 2002:a63:69ca:0:b0:411:994d:1e29 with SMTP id e193-20020a6369ca000000b00411994d1e29mr17200043pgc.118.1657555689581; Mon, 11 Jul 2022 09:08:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657555689; cv=none; d=google.com; s=arc-20160816; b=H/QvejRfOgcn26/fho1thpn0DqU/xL6qHkgosmtLvrQymCmdzSghXLjEviL/9mcQXV NybPSbDM6MD531iXwFP/+hwkpmbYwDsMFaNKrYmq4LLYqFTJfvptNfdqKBiNu+frkQUe h+PdnwpV+k3vKcAylAgiNPyfnQFvzPHe36HvOAJKnB4qev3lEGOumCyng+jO9eU/Wrzb 3Kq2FA7e2NAL28FUwnyN49LoPX7ZWwN0oHF2rDHEdKY0pTn3+nJaJfbmHTKbc4xXHihE dcdlR5g13TJMjxpkjeXJLiB15Qr8T7Ew6FwEOxYOl6HKDRc44uvA4nCSPEqaSug4u/+u EbSw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:organization:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=KxlAUXg7eMS6jzpM4oW+9PvyHNaxoTBwxjCw3hARsfU=; b=JC/NckJsg2DSQE+aWus1DQFBxZGOPnxVrFcfTz4giqAPSuY9oiI4elyc0qnc3SiYZe aMQC/sqcCM7GoKulrMaHh4r/urVLJXiwtuY5JjFqGC8IOQrTkt4PLb0sFH4kLtPcd/tQ 8QBv2eeIg2SDXGvcqiwtW2hetJw2bJf3VJcM9vBKI+AfcqgIOe+bM8MMFPZaxXLoNpR7 sEZCuO7NorV/QP1OF51t2soFR9z/FR8aDAwQq2xIPZe/TqLrKDmAeJ9KnK0bE5ZCXVMZ 79L62HBrI4j/uXDurBZocSGmZQLYm1Sdo/VoZw5KxXXdCkhCsPid4X5iwNVxZZA/RGYn p8EQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=b3sEiSDY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d37-20020a631d25000000b0041291b52146si10809105pgd.256.2022.07.11.09.07.56; Mon, 11 Jul 2022 09:08:09 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=b3sEiSDY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231234AbiGKQFR (ORCPT + 99 others); Mon, 11 Jul 2022 12:05:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56202 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229616AbiGKQFO (ORCPT ); Mon, 11 Jul 2022 12:05:14 -0400 Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AF2D252E4B; Mon, 11 Jul 2022 09:05:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1657555513; x=1689091513; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=tFeOnXMKVHMBMYuxU1nhFxhl70jRU9J1wY/OcsOGdUw=; b=b3sEiSDYtyMA3S9P5phK216FZ16yKhibIdvjqMWNy/a7E9q/5+n+nrdU 9i3Cet6DEs07xoht4OYTqnAh7uLegMClVhKZZofAkvMUx4V8XikV7nQCk dYKHX1t8snypXaPs9ZHdR/HXgowSkJrJ9hfZE3bfFLje4dao0iAp193zV mg195P0o8pj4VKYBTM3hMa0GiLJUW45nGJDxC5r8kEq+JCai09RtCa9fT BGkENWQFGrA6EbLJfmtpWkAM4G/VvtTn88M+oVWTePKs+9LdxYSf4PifF TWxV8bC8Kv0cwkVmAz4KfeOTR+gSCTNQDws2FNVpHdKOl9b55CtfY4CbE Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10405"; a="371008022" X-IronPort-AV: E=Sophos;i="5.92,263,1650956400"; d="scan'208";a="371008022" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Jul 2022 09:05:13 -0700 X-IronPort-AV: E=Sophos;i="5.92,263,1650956400"; d="scan'208";a="592301209" Received: from silpixa00400314.ir.intel.com (HELO silpixa00400314) ([10.237.222.76]) by orsmga007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Jul 2022 09:05:09 -0700 Date: Mon, 11 Jul 2022 17:05:01 +0100 From: Giovanni Cabiddu To: lkp@intel.com, Vlad Dronov , Herbert Xu Cc: kbuild-all@lists.01.org, GNU/Weeb Mailing List , LKML , Tomasz Kowallik , Adam Guerin , Fiona Trahe , Wojciech Ziemba , linux-doc@vger.kernel.org Subject: [PATCH] crypto: qat - fix indentation in ABI documentation Message-ID: References: <202207090803.TEGI95qw-lkp@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Research and Development Ireland Ltd - Co. Reg. #308263 - Collinstown Industrial Park, Leixlip, County Kildare - Ireland X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 11, 2022 at 02:35:07PM +0200, Vlad Dronov wrote: > Hi, > > On Mon, Jul 11, 2022 at 11:32 AM Giovanni Cabiddu > wrote: > > > > On Sat, Jul 09, 2022 at 08:23:35AM +0800, kernel test robot wrote: > ...skip... > > > >> Documentation/ABI/testing/sysfs-driver-qat:24: WARNING: Unexpected indentation. > > > > > > vim +24 Documentation/ABI/testing/sysfs-driver-qat > > > > > > > 24 Date: June 2022 > > I'm not able to spot what the issue is. Any suggestions? > > Same here. I do not see what issue the test robot is reporting. I found what the issue is. It seems Sphinx doesn't like the extra indentation in the sections. ----8<---- From: Giovanni Cabiddu Date: Mon, 11 Jul 2022 16:18:43 +0100 Subject: [PATCH] crypto: qat - fix indentation in ABI documentation Organization: Intel Research and Development Ireland Ltd - Co. Reg. #308263 - Collinstown Industrial Park, Leixlip, County Kildare - Ireland Change the indentation in the file sysfs-driver-qat to resolve the following warning when generating documentation with `make htmldocs`: Documentation/ABI/testing/sysfs-driver-qat:24: WARNING: Unexpected indentation. Fixes: d4cfb144f605 ("crypto: qat - expose device config through sysfs for 4xxx") Reported-by: kernel test robot Signed-off-by: Giovanni Cabiddu --- Documentation/ABI/testing/sysfs-driver-qat | 38 ++++++++++------------ 1 file changed, 17 insertions(+), 21 deletions(-) diff --git a/Documentation/ABI/testing/sysfs-driver-qat b/Documentation/ABI/testing/sysfs-driver-qat index a600531e9562..741d97fa5ae1 100644 --- a/Documentation/ABI/testing/sysfs-driver-qat +++ b/Documentation/ABI/testing/sysfs-driver-qat @@ -8,12 +8,12 @@ Description: Reports the current state of the QAT device and allows to This attribute is RW. Returned values: - up: the device is up and running - down: the device is down + up: the device is up and running + down: the device is down Allowed values: - up: initialize and start the device - down: stop the device and bring it down + up: initialize and start the device + down: stop the device and bring it down It is possible to transition the device from up to down only if the device is up and vice versa. @@ -30,16 +30,12 @@ Description: Reports the current configuration of the QAT device and allows This attribute is RW. Returned values: - sym;asym: the device is configured for running - crypto services - dc: the device is configured for running - compression services + sym;asym: the device is configured for running crypto services + dc: the device is configured for running compression services Allowed values: - sym;asym: configure the device for running - crypto services - dc: configure the device for running - compression services + sym;asym: configure the device for running crypto services + dc: configure the device for running compression services It is possible to set the configuration only if the device is in the `down` state (see /sys/bus/pci/devices//qat/state) @@ -47,14 +43,14 @@ Description: Reports the current configuration of the QAT device and allows The following example shows how to change the configuration of a device configured for running crypto services in order to run data compression: - # cat /sys/bus/pci/devices//qat/state - up - # cat /sys/bus/pci/devices//qat/cfg_services - sym;asym - # echo down > /sys/bus/pci/devices//qat/state - # echo dc > /sys/bus/pci/devices//qat/cfg_services - # echo up > /sys/bus/pci/devices//qat/state - # cat /sys/bus/pci/devices//qat/cfg_services - dc + # cat /sys/bus/pci/devices//qat/state + up + # cat /sys/bus/pci/devices//qat/cfg_services + sym;asym + # echo down > /sys/bus/pci/devices//qat/state + # echo dc > /sys/bus/pci/devices//qat/cfg_services + # echo up > /sys/bus/pci/devices//qat/state + # cat /sys/bus/pci/devices//qat/cfg_services + dc This attribute is only available for qat_4xxx devices. -- 2.36.1