[PATCH 2/2] Documentation: Fix filenames for remoteproc/rpmsg

[Daniel Baluta <daniel.baluta@nxp.com>]

Fix rpmsg and remoteproc filenames references after moving
them out of staging.

Signed-off-by: Daniel Baluta <daniel.baluta@nxp.com>
---
 Documentation/driver-api/remoteproc.rst | 2 +-
 Documentation/driver-api/rpmsg.rst      | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/driver-api/remoteproc.rst b/Documentation/driver-api/remoteproc.rst
index 5c226fa076d6..d7ff4694aba6 100644
--- a/Documentation/driver-api/remoteproc.rst
+++ b/Documentation/driver-api/remoteproc.rst
@@ -357,4 +357,4 @@ rpmsg virtio devices this way, if desired).
 Of course, RSC_VDEV resource entries are only good enough for static
 allocation of virtio devices. Dynamic allocations will also be made possible
 using the rpmsg bus (similar to how we already do dynamic allocations of
-rpmsg channels; read more about it in rpmsg.txt).
+rpmsg channels; read more about it in rpmsg.rst).
diff --git a/Documentation/driver-api/rpmsg.rst b/Documentation/driver-api/rpmsg.rst
index 40282cca86ca..a50c4db6679f 100644
--- a/Documentation/driver-api/rpmsg.rst
+++ b/Documentation/driver-api/rpmsg.rst
@@ -5,8 +5,8 @@ Remote Processor Messaging (rpmsg) Framework
 .. note::
 
   This document describes the rpmsg bus and how to write rpmsg drivers.
-  To learn how to add rpmsg support for new platforms, check out remoteproc.txt
-  (also a resident of Documentation/).
+  To learn how to add rpmsg support for new platforms, check out remoteproc.rst
+  (also a resident of Documentation/driver-api).
 
 Introduction
 ============
-- 
2.45.2