From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linux ACPI <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Hans de Goede <hansg@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Armin Wolf <w_armin@gmx.de>,
Colin Ian King <colin.i.king@gmail.com>,
acpica-devel@lists.linux.dev,
Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>,
Pawel Chmielewski <pawel.chmielewski@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>
Subject: [PATCH v1 3/3] ACPI: Update upstream ACPICA repository URL in documentation
Date: Wed, 19 Aug 2026 22:14:10 +0200 [thread overview]
Message-ID: <1867400.VLH7GnMWUR@rafael.j.wysocki> (raw)
In-Reply-To: <7982261.EvYhyI6sBW@rafael.j.wysocki>
From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Update the URL of the upstream ACPICA repository after recent changes in
the upstream ACPICA project.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
Documentation/driver-api/acpi/linuxized-acpica.rst | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
--- a/Documentation/driver-api/acpi/linuxized-acpica.rst
+++ b/Documentation/driver-api/acpi/linuxized-acpica.rst
@@ -117,7 +117,7 @@ ACPICA Release
==============
The ACPICA project maintains its code base at the following repository URL:
-https://github.com/acpica/acpica.git. As a rule, a release is made every
+https://github.com/open-acpica/acpica.git. As a rule, a release is made every
month.
As the coding style adopted by the ACPICA project is not acceptable by
@@ -173,7 +173,7 @@ illustrated in the following figure::
utility located in source/tools/acpisrc folder and a number of
scripts located in generate/linux folder.
B. acpica / master - "master" branch of the git repository at
- <https://github.com/acpica/acpica.git>.
+ <https://github.com/open-acpica/acpica.git>.
C. linux-pm / linux-next - "linux-next" branch of the git repository at
<https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git>.
D. linux / master - "master" branch of the git repository at
@@ -244,7 +244,7 @@ before they become available from the AC
Then the gen-patch.sh command can help to cherry-pick an ACPICA commit
from the ACPICA local repository::
- $ git clone https://github.com/acpica/acpica
+ $ git clone https://github.com/open-acpica/acpica
$ cd acpica
$ generate/linux/gen-patch.sh -u [commit ID]
@@ -259,7 +259,7 @@ before they become available from the AC
You can generate the ACPICA release series yourself and rebase your code on
top of the generated ACPICA release patches::
- $ git clone https://github.com/acpica/acpica
+ $ git clone https://github.com/open-acpica/acpica
$ cd acpica
$ generate/linux/make-patches.sh -u [commit ID]
@@ -273,7 +273,7 @@ before they become available from the AC
If you have local copies of both Linux and upstream ACPICA, you can generate
a diff file indicating the state of the current divergences::
- # git clone https://github.com/acpica/acpica
+ # git clone https://github.com/open-acpica/acpica
# git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
# cd acpica
# generate/linux/divergence.sh -s ../linux
next prev parent reply other threads:[~2026-08-19 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 20:11 [PATCH v1 0/3] ACPI: Updates related to upstream ACPICA project changes Rafael J. Wysocki
2026-08-19 20:12 ` [PATCH v1 1/3] ACPI: Add Bob Moore to CREDITS Rafael J. Wysocki
2026-08-19 20:13 ` [PATCH v1 2/3] ACPI: Update MAINTAINERS entry for ACPICA Rafael J. Wysocki
2026-08-19 20:14 ` Rafael J. Wysocki [this message]
2026-08-20 17:12 ` [PATCH v1 0/3] ACPI: Updates related to upstream ACPICA project changes Armin Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1867400.VLH7GnMWUR@rafael.j.wysocki \
--to=rafael@kernel.org \
--cc=acpica-devel@lists.linux.dev \
--cc=andriy.shevchenko@linux.intel.com \
--cc=colin.i.king@gmail.com \
--cc=hansg@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=lukasz.luba@arm.com \
--cc=maciej.wieczor-retman@intel.com \
--cc=pawel.chmielewski@intel.com \
--cc=sudeep.holla@arm.com \
--cc=w_armin@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox