From: anish kumar <yesanishhere@gmail.com>
To: ohad@wizery.com, bjorn.andersson@linaro.org,
mathieu.poirier@linaro.org, corbet@lwn.net
Cc: linux-remoteproc@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
anish kumar <yesanishhere@gmail.com>
Subject: [PATCH 1/7] Documentation: remoteproc: move from staging
Date: Tue, 22 Oct 2024 14:35:10 -0700 [thread overview]
Message-ID: <20241022213516.1756-2-yesanishhere@gmail.com> (raw)
In-Reply-To: <20241022213516.1756-1-yesanishhere@gmail.com>
In preparation for upcoming enhancements, this
commit relocates the existing documentation
from the staging area to the mainline Documentation
directory. Future patches will add further
documentation to improve clarity and usability.
Signed-off-by: anish kumar <yesanishhere@gmail.com>
---
Documentation/{staging => remoteproc}/remoteproc.rst | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename Documentation/{staging => remoteproc}/remoteproc.rst (100%)
diff --git a/Documentation/staging/remoteproc.rst b/Documentation/remoteproc/remoteproc.rst
similarity index 100%
rename from Documentation/staging/remoteproc.rst
rename to Documentation/remoteproc/remoteproc.rst
--
2.39.3 (Apple Git-146)
next prev parent reply other threads:[~2024-10-22 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 21:35 [PATCH 0/1] remoteproc documentation changes anish kumar
2024-10-22 21:35 ` anish kumar [this message]
2024-10-22 21:35 ` [PATCH 2/7] Documentation: remoteproc: add more information anish kumar
2024-10-22 21:35 ` [PATCH 3/7] Remoteproc: Documentation: add the main index anish kumar
2024-10-22 21:47 ` Jonathan Corbet
2024-10-22 21:35 ` [PATCH 4/7] Remoteproc: Documentation: add driver api anish kumar
2024-10-22 21:35 ` [PATCH 5/7] Remoteproc: Documentation: add userspace api anish kumar
2024-10-22 21:35 ` [PATCH 6/7] MAINTAINERS: remoteproc documentation path update anish kumar
2024-10-22 21:35 ` [PATCH 7/7] rpmsg: Documentation: update the path anish kumar
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=20241022213516.1756-2-yesanishhere@gmail.com \
--to=yesanishhere@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=ohad@wizery.com \
/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