From patchwork Tue Jun 23 07:09:05 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Mauro Carvalho Chehab X-Patchwork-Id: 11619893 Return-Path: Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 55399618 for ; Tue, 23 Jun 2020 07:10:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 322A920772 for ; Tue, 23 Jun 2020 07:10:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592896211; bh=sTFjDVFNxvaxYL1XIBkVBYNkDxJgnmCW7W2tRtvvhLM=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=o2+3ERKwGYMH36sGy4++siMYVsGeet67n78xxrHFmzeMZnRNzHbtF1tX5j1TwfR94 Yb/ufk40YhJCjf8nwLGRvyVmkhl2I5MQoIAOl7vNZxHF9blF+kumr/LcmgliAsBJ8J orpdi8rnipUUSLNEvGT0JLgnATpJgQJN4Ks608m4= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731313AbgFWHKC (ORCPT ); Tue, 23 Jun 2020 03:10:02 -0400 Received: from mail.kernel.org ([198.145.29.99]:39932 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731306AbgFWHJQ (ORCPT ); Tue, 23 Jun 2020 03:09:16 -0400 Received: from mail.kernel.org (unknown [95.90.213.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 69B58207D8; Tue, 23 Jun 2020 07:09:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592896155; bh=sTFjDVFNxvaxYL1XIBkVBYNkDxJgnmCW7W2tRtvvhLM=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=m++TRjfKXjCGKujF4infLuDUtr+4rY07SzmgNgJUzP0lIpre7KbvVx9a/U1bmWWsX zqdDkcgPvulkmmoqmK0NhqQwz75nvw2JhXeSg22823VDBErEq9pzNCTVzCAX6afbjH LzqNoOqBlBdah9HYIbo/FYSpvWpydFHL5KqUsQFQ= Received: from mchehab by mail.kernel.org with local (Exim 4.93) (envelope-from ) id 1jnd3R-003qjG-8Q; Tue, 23 Jun 2020 09:09:13 +0200 From: Mauro Carvalho Chehab To: Linux Doc Mailing List Cc: Mauro Carvalho Chehab , linux-kernel@vger.kernel.org, Jonathan Corbet , Shuah Khan , Sandipan Das , Stephen Rothwell , Ram Pai , Thiago Jung Bauermann , Dave Hansen , linux-kselftest@vger.kernel.org Subject: [PATCH v2 09/15] selftests/vm/keys: fix a broken reference at protection_keys.c Date: Tue, 23 Jun 2020 09:09:05 +0200 Message-Id: X-Mailer: git-send-email 2.26.2 In-Reply-To: References: MIME-Version: 1.0 Sender: linux-kselftest-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kselftest@vger.kernel.org Changeset 1eecbcdca2bd ("docs: move protection-keys.rst to the core-api book") from Jun 7, 2019 converted protection-keys.txt file to ReST. A recent change at protection_keys.c partially reverted such changeset, causing it to point to a non-existing file: - * Tests x86 Memory Protection Keys (see Documentation/core-api/protection-keys.rst) + * Tests Memory Protection Keys (see Documentation/vm/protection-keys.txt) It sounds to me that the changeset that introduced such change 4645e3563673 ("selftests/vm/pkeys: rename all references to pkru to a generic name") could also have other side effects, as it sounds that it was not generated against uptream code, but, instead, against a version older than Jun 7, 2019. Fixes: 4645e3563673 ("selftests/vm/pkeys: rename all references to pkru to a generic name") Signed-off-by: Mauro Carvalho Chehab --- tools/testing/selftests/vm/protection_keys.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/selftests/vm/protection_keys.c b/tools/testing/selftests/vm/protection_keys.c index fc19addcb5c8..fdbb602ecf32 100644 --- a/tools/testing/selftests/vm/protection_keys.c +++ b/tools/testing/selftests/vm/protection_keys.c @@ -1,6 +1,6 @@ // SPDX-License-Identifier: GPL-2.0 /* - * Tests Memory Protection Keys (see Documentation/vm/protection-keys.txt) + * Tests Memory Protection Keys (see Documentation/core-api/protection-keys.rst) * * There are examples in here of: * * how to set protection keys on memory