linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 02/10] docs: vcpu-requests.rst: fix reference for atomic ops
Date: Wed, 19 May 2021 10:51:39 +0200	[thread overview]
Message-ID: <703af756ac26a06c2185c05dfe6d902253f11161.1621413933.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1621413933.git.mchehab+huawei@kernel.org>

Changeset f0400a77ebdc ("atomic: Delete obsolete documentation")
got rid of atomic_ops.rst, pointing that this was superseded by
Documentation/atomic_*.txt.

Update its reference accordingly.

Fixes: f0400a77ebdc ("atomic: Delete obsolete documentation")
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
 Documentation/virt/kvm/vcpu-requests.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/virt/kvm/vcpu-requests.rst b/Documentation/virt/kvm/vcpu-requests.rst
index 5feb3706a7ae..5f8798e7fdf8 100644
--- a/Documentation/virt/kvm/vcpu-requests.rst
+++ b/Documentation/virt/kvm/vcpu-requests.rst
@@ -302,6 +302,6 @@ VCPU returns from the call.
 References
 ==========
 
-.. [atomic-ops] Documentation/core-api/atomic_ops.rst
+.. [atomic-ops] Documentation/atomic_bitops.txt and Documentation/atomic_t.txt
 .. [memory-barriers] Documentation/memory-barriers.txt
 .. [lwn-mb] https://lwn.net/Articles/573436/
-- 
2.31.1


  parent reply	other threads:[~2021-05-19  8:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19  8:51 [PATCH 00/10] Documentation build warning fixes Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 01/10] docs: update sysfs-platform_profile.rst reference Mauro Carvalho Chehab
2021-05-19  8:51 ` Mauro Carvalho Chehab [this message]
2021-05-19  8:51 ` [PATCH 03/10] docs: translations/zh_CN: fix a typo at 8.Conclusion.rst Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 04/10] docs: sched-bwc.rst: fix a typo on a doc name Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 05/10] docs: update pin-control.rst references Mauro Carvalho Chehab
2021-05-19 10:20   ` Charles Keepax
2021-05-19 14:43   ` Lee Jones
2021-05-25  0:30   ` Linus Walleij
2021-05-19  8:51 ` [PATCH 06/10] docs: virt: api.rst: fix a pointer to SGX documentation Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 07/10] docs: ABI: iommu: remove duplicated definition for sysfs-kernel-iommu_groups Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 08/10] docs: ABI: sysfs-class-backlight: unify ambient light zone nodes Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 09/10] docs: ABI: sysfs-class-led-trigger-pattern: remove repeat duplication Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 10/10] iio: documentation: fix a typo Mauro Carvalho Chehab
2021-05-20 20:08   ` Matthew Wilcox
2021-05-20 20:00 ` [PATCH 00/10] Documentation build warning fixes Jonathan Corbet

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=703af756ac26a06c2185c05dfe6d902253f11161.1621413933.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=corbet@lwn.net \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).