Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp3487230imw; Mon, 11 Jul 2022 09:31:21 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vXsqUz6f1arMWE4m5NXpYMGNWMhrZFlnPEQqhCLIx5DUDyy+8olsXxIwFxR27RkfazQltu X-Received: by 2002:a17:903:1246:b0:16b:7f81:138 with SMTP id u6-20020a170903124600b0016b7f810138mr19144314plh.141.1657557080844; Mon, 11 Jul 2022 09:31:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657557080; cv=none; d=google.com; s=arc-20160816; b=pPealxXcyEACSaatvvPg8tBIQanE5ZMtBryaWr8oviPQPNSQy0H6aVbq5m/OG90t4Q exoKCXdzURLC2QDU+GT4ZIhJLON9p3CY670wyECx5w+OKvuKUnIg0ZqWdB7TRktchZPz 1VfoEZKILkHb+M3tVxHmMA/ts7LgAMLW1R1ZP4IFK1OSuAMiskMyVrAkCjt+53WTOkpk SFCzExUHPtm+86Qk06mZwWbjIg6r5EmyLTZ6rcJiMCa5IHJxUsq9P650I9upjI66pGo4 7nmkoZTdyx+LVWUZ8ZK1Vq0VUUGVeUPqElOwbES8b0QGZBazt5Y11Unc9PLgiAglS59Z 56Cw== 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=xKIurUzuWYCSuLd1A8qenNdAQSpSFDioyf6zlSKZsp0=; b=qI4o7MgMOXHuoYl7rF9FF6Jlj1HIQlKO1Ak7EGMmWZHwhoc70nvz+bDpmkW6ez6uTa VHWB7zvz42SBTw8YTKELlrgF6PzMux3Askta1ygrcwWQxcsaU9eNGm0czYvnsY/chi68 5DBnQjrg69QusICSCN/YDm7G6MDxOQnNQxT3tDRvU6NmjBuaBRlWkY7HB2OmkGD1bM8y Jr0Q1ZetV21ryY1V5J/qrL6XtFp0yzdpoHCpxPRThM5jK/m7/imQ0AcjOqYz4hAXpU0V A8qo9YZ85N6ZPAV68JXnywLqsQ09eRiRmme0DslSndh/u7bN929ZSr9qDFhi0kdobH8i ozuQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=LtMk+Dts; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-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 k7-20020a170902d58700b0016c0ae33e3esi10063238plh.347.2022.07.11.09.30.55; Mon, 11 Jul 2022 09:31:20 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-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=LtMk+Dts; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-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 S229853AbiGKQaT (ORCPT + 99 others); Mon, 11 Jul 2022 12:30:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52082 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230247AbiGKQaS (ORCPT ); Mon, 11 Jul 2022 12:30:18 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6D8221BE94; Mon, 11 Jul 2022 09:30:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1657557017; x=1689093017; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=M7gQthUQ8v0LKr/DjxFP5tYXmCHQe3FMOrvQefnZBAQ=; b=LtMk+DtscddZ7bXbLNwXgG3JsJc5kNcsh94PKXnkGgFNUif+lB1wjc+0 ExcO7HqYcuUDu9WJkjMiS2BCkOmGFXZO6c6I8SDKe5VkxLLbNaLKo7Yqx fX2+UJy5BRXK1ez37lOiQW3jXYANpx0Oz0U6bUuA6OCVWqo5Xj37tQd/k B3kcQgvhEMk4XEZD0xbiPb0FymJy2nYdO0mfwuS2cvJgfp1nBMc4rfomf 3I25UJ+r5mrsk9bOQN92lQ47Q8yeI5bNnCJ+6V++61pq6suJLO9LRsJjp qa0Yn/ZFQ19oQtRYm+u6Dl+q0aaBXG2Lkxi2IljtiaHRuR2YR9eIdGJs3 A==; X-IronPort-AV: E=McAfee;i="6400,9594,10405"; a="282257602" X-IronPort-AV: E=Sophos;i="5.92,263,1650956400"; d="scan'208";a="282257602" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Jul 2022 09:29:52 -0700 X-IronPort-AV: E=Sophos;i="5.92,263,1650956400"; d="scan'208";a="921846535" Received: from silpixa00400314.ir.intel.com (HELO silpixa00400314) ([10.237.222.76]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Jul 2022 09:29:49 -0700 Date: Mon, 11 Jul 2022 17:29:39 +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, linux-crypto@vger.kernel.org Subject: Re: [PATCH RESEND] 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=-7.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, 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-crypto@vger.kernel.org On Mon, Jul 11, 2022 at 05:05:18PM +0100, Giovanni Cabiddu wrote: > 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. Resending including linux-crypto. Apologies for the duplicate. ----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