From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BA4E13128BA; Fri, 29 Aug 2025 12:18:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.19 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756469934; cv=none; b=j+avQN4WhEr7qXpDuA/3nhceLiCx2nMLiANtB4U3xGPsCcmFsdKQ73zdCesgJvKUYW3Gkjk5YeEWLfpsdkuT7kThPTFWA5UeDUkP1Qy8FCufqzoQS1OSATLB+fOkIIqiq2ErXMnOoiY2ormYdotsQ6vTGLhuxRLtU1dCLDRSIgc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756469934; c=relaxed/simple; bh=lmOaDJrWsALHNdIkFkPEn+1/tHhvy8ASz+0CpcTOxMQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=aixO4Udse8s1/Be5EQ+hm5B9V1oK4EoGuqdUm4w7WZN6OgfQjs9oDhXgFjHHuKBX6oB6pN/VihjWOlSnlzAU7WZg5OrRBnvWeTs7xPkgdvtSa+K9u01GU0NVVPZOrZ1nq17ue8hc+/U1WWO2OoUou5xWsMxaTmWf/Yo/c/qSaoU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=JQ0/AxIO; arc=none smtp.client-ip=198.175.65.19 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="JQ0/AxIO" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1756469933; x=1788005933; h=from:to:cc:subject:in-reply-to:references:date: message-id:mime-version; bh=lmOaDJrWsALHNdIkFkPEn+1/tHhvy8ASz+0CpcTOxMQ=; b=JQ0/AxIOhGOdNMLF+qwZWK/qJiXTSwfEjc9AjX87xrVNj81JYdTRUYja V7Zb2LTkZJLsheaBDsqGMptJ5WLRby9tzbmbVTPMLbVDGXjofwZLzfW44 uOWocqbtuuJjlRsXxevgLMALWmEsvl5IiIVUgq/yRnlEAAkyhKziMiGiq 8LQ0HYP1ZzdKGkkj3GmzQUSZySM6I71X9QFAhieJDOOWEHkEahigArV0G EZKhduHmce0JLMY2Jfh70zm2ysBhf+FZp5eGkImBMlzoWCDD2/UUeD67o gUoOPBKJW64YrJe4R/5lKaE/2DIWL5soyk1zj202MgephKE5eRnOICCye A==; X-CSE-ConnectionGUID: HteoTLb2Tjy5YxO8qrXg+A== X-CSE-MsgGUID: J3mI7IycSxOWSYmo7wvxqg== X-IronPort-AV: E=McAfee;i="6800,10657,11536"; a="58603807" X-IronPort-AV: E=Sophos;i="6.18,221,1751266800"; d="scan'208";a="58603807" Received: from fmviesa009.fm.intel.com ([10.60.135.149]) by orvoesa111.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Aug 2025 05:18:51 -0700 X-CSE-ConnectionGUID: FceyOGKfTMK8J/ArNXLz6w== X-CSE-MsgGUID: nahg4MG6QSGDgmwgF/j0Ug== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.18,221,1751266800"; d="scan'208";a="170753940" Received: from hrotuna-mobl2.ger.corp.intel.com (HELO localhost) ([10.245.246.58]) by fmviesa009-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Aug 2025 05:18:22 -0700 From: Jani Nikula To: Bagas Sanjaya , Linux Kernel Mailing List , Linux Documentation , Linux DAMON , Linux Memory Management List , Linux Power Management , Linux Block Devices , Linux BPF , Linux Kernel Workflows , Linux KASAN , Linux Devicetree , Linux fsverity , Linux MTD , Linux DRI Development , Linux Kernel Build System , Linux Networking , Linux Sound Cc: Thomas Gleixner , Borislav Petkov , Peter Zijlstra , Josh Poimboeuf , Pawan Gupta , Jonathan Corbet , SeongJae Park , Andrew Morton , David Hildenbrand , Lorenzo Stoakes , "Liam R. Howlett" , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , Huang Rui , "Gautham R. Shenoy" , Mario Limonciello , Perry Yuan , Jens Axboe , Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Martin KaFai Lau , Eduard Zingerman , Song Liu , Yonghong Song , John Fastabend , KP Singh , Stanislav Fomichev , Hao Luo , Jiri Olsa , Dwaipayan Ray , Lukas Bulwahn , Joe Perches , Andrey Ryabinin , Alexander Potapenko , Andrey Konovalov , Dmitry Vyukov , Vincenzo Frascino , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Eric Biggers , tytso@mit.edu, Richard Weinberger , Zhihao Cheng , David Airlie , Simona Vetter , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Nathan Chancellor , Nicolas Schier , Ingo Molnar , Will Deacon , Boqun Feng , Waiman Long , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Simon Horman , Shay Agroskin , Arthur Kiyanovski , David Arinzon , Saeed Bishara , Andrew Lunn , Liam Girdwood , Mark Brown , Jaroslav Kysela , Takashi Iwai , Alexandru Ciobotaru , The AWS Nitro Enclaves Team , Jesper Dangaard Brouer , Bagas Sanjaya , Laurent Pinchart , Steve French , Meetakshi Setiya , Greg Kroah-Hartman , "Martin K. Petersen" , Bart Van Assche , Thomas =?utf-8?Q?Wei=C3=9Fschuh?= , Masahiro Yamada Subject: Re: [PATCH 00/14] Internalize www.kernel.org/doc cross-reference In-Reply-To: <20250829075524.45635-1-bagasdotme@gmail.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20250829075524.45635-1-bagasdotme@gmail.com> Date: Fri, 29 Aug 2025 15:18:20 +0300 Message-ID: <437912a24e94673c2355a2b7b50c3c4b6f68fcc6@intel.com> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Fri, 29 Aug 2025, Bagas Sanjaya wrote: > Cross-references to other docs (so-called internal links) are typically > done following Documentation/doc-guide/sphinx.rst: either simply > write the target docs (preferred) or use :doc: or :ref: reST directives > (for use-cases like having anchor text or cross-referencing sections). > In some places, however, links to https://www.kernel.org/doc > are used instead (outgoing, external links), owing inconsistency as > these requires Internet connection only to see docs that otherwise > can be accessed locally (after building with ``make htmldocs``). > > Convert such external links to internal links. Note that this does not > cover docs.kernel.org links nor touching Documentation/tools (as > docs containing external links are in manpages). FWIW, I'd much prefer using :ref: on rst anchors (that automatically pick the link text from the target heading) instead of manually adding link texts and file references. i.e. .. _some_target: Heading After Some Target ========================= See :ref:`some_target`. Will generate "See Heading After Some Target". BR, Jani. -- Jani Nikula, Intel