Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp46701pxb;
        Wed, 18 Nov 2020 16:07:52 -0800 (PST)
X-Google-Smtp-Source: ABdhPJyTLwCrv8tQrz3bpUJ43m3hIDI/QhAWTOwClRFO+x4mHtHDTVi0lGTELFyzYBAIKYLuK5PJ
X-Received: by 2002:aa7:d54b:: with SMTP id u11mr29171974edr.341.1605744472487;
        Wed, 18 Nov 2020 16:07:52 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1605744472; cv=none;
        d=google.com; s=arc-20160816;
        b=BDMvUdN5EHFNzV7FcPV5WibSkRcF5R/W9tVnToFeCOkCL0t13/KEeVQjhYvNKL9Uj5
         5xHSU9WnueEIf0EKtggtmWT0iwfbl1wxXp3SaRP9ixAM/gk1JxVTnIavahcT5yCltcXP
         79qb9Z8nf68iVodbsmiMeyXWyKD9mrV2VvNKKdghs6weq+hsLfRH4lzyK6PPiXx3vS6s
         lBemJ8iy/Z/4tLjtnd3eVcRUgirU4hnXFuJqO7UchJXLySdRw+46/Wy8QzINLEGehFzW
         3O+73bW6ORacSumpyRcgWyM/pGx1USgvJ+Bh6OFYwrdiVVJMTyYWsF5A6wk8xKmXppZ/
         sOwQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=list-id:precedence:content-transfer-encoding:mime-version
         :organization:references:in-reply-to:message-id:subject:cc:to:from
         :date;
        bh=ADXQ4R4gsjOnealPM7PLwJHFJ2u0vCvHXdQuJ9+YnGA=;
        b=gtrSoFNSgepKPFL2xqlt05jUXM6tpShxdOPY0iydJysF7cDJU6EtvrT4Eai7L0bg45
         lfDUIOmPDdmeHCu9dB54y8JjVtaElYotw9eP+U9rUb1GTPKwUUChUFuta3tQ/BCnpFWA
         YWzSEdRYjMaLgQZ6WS+QHUbXA1qiKbU49e7A+NQB3Q5piTyuIx7uGgd7ONe9CXBq0s+x
         nvemSM9Sjx0EMgdrztgDClnPqQa+ybqK4v9XFYPN6UlEq2y6X1GuA5194gJDjFu2+XZz
         oAnsSTfcmOfHoOGBP+/tBrsjpSNRupwNUf7FF788W4bVXivlhSPsaZI7LAE0upiRhi2z
         vNiw==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18])
        by mx.google.com with ESMTP id p7si17465699edx.415.2020.11.18.16.07.19;
        Wed, 18 Nov 2020 16:07:52 -0800 (PST)
Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1726110AbgKSAFs (ORCPT <rfc822;huangweiredhat@gmail.com>
        + 99 others); Wed, 18 Nov 2020 19:05:48 -0500
Received: from ms.lwn.net ([45.79.88.28]:47404 "EHLO ms.lwn.net"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1725947AbgKSAFs (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 18 Nov 2020 19:05:48 -0500
Received: from lwn.net (localhost [127.0.0.1])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by ms.lwn.net (Postfix) with ESMTPSA id 4F6412B2;
        Thu, 19 Nov 2020 00:05:48 +0000 (UTC)
Date:   Wed, 18 Nov 2020 17:05:47 -0700
From:   Jonathan Corbet <corbet@lwn.net>
To:     Thorsten Leemhuis <linux@leemhuis.info>
Cc:     Randy Dunlap <rdunlap@infradead.org>, linux-doc@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 08/26] docs: reporting-bugs: make readers check
 the taint flag
Message-ID: <20201118170547.4fabd38b@lwn.net>
In-Reply-To: <d21b7ead04852d3de7dd6892fe5e27aca1f345ff.1605203187.git.linux@leemhuis.info>
References: <cover.1605203187.git.linux@leemhuis.info>
        <d21b7ead04852d3de7dd6892fe5e27aca1f345ff.1605203187.git.linux@leemhuis.info>
Organization: LWN.net
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, 12 Nov 2020 18:58:45 +0100
Thorsten Leemhuis <linux@leemhuis.info> wrote:

> +If your kernel is tainted, study
> +:ref:`Documentation/admin-guide/tainted-kernels.rst <taintedkernels>` to find
> +out why. Try to eliminate the reason. Often it's caused by one these three
> +things:

One little detail that jumped at me just now: the automarkup extension now
understands Documentation/whatever and makes a cross-reference, so there's
no need for an explicit :ref: for those.

Thanks,

jon