Received: by 2002:a05:6358:45e:b0:b5:b6eb:e1f9 with SMTP id 30csp1024812rwe; Thu, 1 Sep 2022 11:10:53 -0700 (PDT) X-Google-Smtp-Source: AA6agR4xnPUEtBOMj1cnj0o9CVYObCCo63ARpktdicB5hgnV3/EApqDYFOnlbyu2OtqZ9Tue0GI8 X-Received: by 2002:a17:907:6e02:b0:741:6c3a:4b45 with SMTP id sd2-20020a1709076e0200b007416c3a4b45mr15809288ejc.80.1662055853296; Thu, 01 Sep 2022 11:10:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1662055853; cv=none; d=google.com; s=arc-20160816; b=v+EANhTLyjZherTp+sU9pjFNf6squlpyeSBlQHvPxOi1dlakG2O/QA04jY/NQ1lHZS G9mOvG/JtY1kL83bZASY7YNi2nPaUzRwQkvvRD/Y4U82pO2fzE55oFKCwbeAC6vSU+NN X/4pBae9LkhPfWd4VvNrYzD0bnoaXKGZZeq9EsG1mTeKK9JsD23JEHmc1P2iEtulwxPV /O4UZDekwLFJ+CyXfofKByxYCSoXzoeHwzfFr7urw4y40hPNO/qlfdObfxm4/qwBxuhD TIMkXm5Mg8g9dgr9MLwAbsA3NlXt7xnw19bwe171pz24THMDqN9QUKFJqKBUYXcjeI08 WYQQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=QrKvYZk+5Q1k2RA0sa27ND09zWbRxlQTP/OMwzpnp2o=; b=q/s5JgB/owTc2g/oEr30xAy+YNuu/ByNg20j7Xw8MoB/aWqz49KjJPA/EjpxtLFwVE zotxc/ErzqhOt/PZR7srmLSP1Hm1bSDZ2MWASyGOSC68P6IxOAKnK72P8EEjVFA/90GW iU7vYy7DUYUn+7eNFo4bz+Idyps7zbRSbBoToixwIj41LJjdCBT5TOi/tz09O+z5YKb5 uVo7fvDrKkPYOBA8t37J4L9GJK3wDlqefP+P8rDWStFWOy7UbjUWjtsCJZS4t+ws2lb4 fdfGZy25DOcTDt1gtxRwVtNr980se/JJesm01rQfgc5ACw/NEjEHB362WYSUFnpzIzJd 8jgw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b="I/viAXs2"; 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=linuxfoundation.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id rh16-20020a17090720f000b007418427c7b4si7669901ejb.293.2022.09.01.11.10.19; Thu, 01 Sep 2022 11:10:53 -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=@linuxfoundation.org header.s=korg header.b="I/viAXs2"; 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=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233382AbiIASKG (ORCPT + 99 others); Thu, 1 Sep 2022 14:10:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56240 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232987AbiIASJ6 (ORCPT ); Thu, 1 Sep 2022 14:09:58 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0951512605; Thu, 1 Sep 2022 11:09:57 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id B718AB81BDF; Thu, 1 Sep 2022 18:09:55 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D736FC433D6; Thu, 1 Sep 2022 18:09:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1662055794; bh=PeWtP00smkSpUEiQrOJA6rliFGmYI4kqQTePTz49dyc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=I/viAXs2cJKyQ2EUZ6PMYdDcEO6cVIz3EpeLLpUXJJF2rnagRnT0t144sE2LyYrBo EfNGD3GRtupFph2X9hW1pu2RC6g0+folrgGOuvebbtr64zuMrV9cXlm3G9jbS/J5u9 Zloihw3Cyhx/UJlCiAGy+H6Gq6/aPXvqxoZp0+bk= Date: Thu, 1 Sep 2022 20:09:51 +0200 From: Greg KH To: Eric Biggers Cc: Kai Ye , herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, wangzhou1@hisilicon.com, liulongfang@huawei.com Subject: Re: [PATCH v7 2/3] Documentation: add a isolation strategy sysfs node for uacce Message-ID: References: <20220806022943.47292-1-yekai13@huawei.com> <20220806022943.47292-3-yekai13@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-7.1 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_PASS,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 Thu, Sep 01, 2022 at 10:00:40AM -0700, Eric Biggers wrote: > On Thu, Sep 01, 2022 at 05:04:08PM +0200, Greg KH wrote: > > On Sat, Aug 06, 2022 at 10:29:42AM +0800, Kai Ye wrote: > > > Update documentation describing sysfs node that could help to > > > configure isolation strategy for users in the user space. And > > > describing sysfs node that could read the device isolated state. > > > > > > Signed-off-by: Kai Ye > > > --- > > > Documentation/ABI/testing/sysfs-driver-uacce | 26 ++++++++++++++++++++ > > > 1 file changed, 26 insertions(+) > > > > > > diff --git a/Documentation/ABI/testing/sysfs-driver-uacce b/Documentation/ABI/testing/sysfs-driver-uacce > > > index 08f2591138af..e09fd160d3fa 100644 > > > --- a/Documentation/ABI/testing/sysfs-driver-uacce > > > +++ b/Documentation/ABI/testing/sysfs-driver-uacce > > > @@ -19,6 +19,32 @@ Contact: linux-accelerators@lists.ozlabs.org > > > Description: Available instances left of the device > > > Return -ENODEV if uacce_ops get_available_instances is not provided > > > > > > +What: /sys/class/uacce//isolate_strategy > > > +Date: Jul 2022 > > > > July was a while ago, you sent this patch in August :( > > > > Does the date in the sysfs documentation files serve any purpose besides making > people have to update their patchsets every month? > > The kernel version number would be more useful to readers of the documentation, > and it wouldn't have to be updated quite as often. True, I have seen people use that instead, or no date at all, I don't require it. But if you do put the field in there, it should at least be correct :) thanks, greg k-h