From: Daniel Baluta <daniel.baluta@nxp.com>
To: corbet@lwn.net, andersson@kernel.org, mathieu.poirier@linaro.org
Cc: dan.j.williams@intel.com, cedric.xing@intel.com,
pasha.tatashin@soleen.com, kevin.tian@intel.com,
skhawaja@google.com, daniel.baluta@nxp.com,
yesanishhere@gmail.com, taimoorzaeem@gmail.com,
linux@treblig.org, arnaud.pouliquen@foss.st.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-remoteproc@vger.kernel.org, rdunlap@infradead.org,
daniel.baluta@gmail.com, imx@lists.linux.dev
Subject: [PATCH 0/2] Documentation: Move rpmsg.rst and remoteproc.rst out of staging
Date: Fri, 14 Nov 2025 08:57:43 +0200 [thread overview]
Message-ID: <20251114065746.901649-1-daniel.baluta@nxp.com> (raw)
Try to find a better place for rpmsg.rst and remoteproc.rst files.
Having them in staging suggest that rpmsg / remoteproc are not mature
enough which is not true.
Daniel Baluta (2):
Documentation: Move rpmsg.rst and remoteproc.rst out of staging
Documentation: Fix filenames for remoteproc/rpmsg
Documentation/driver-api/index.rst | 2 ++
Documentation/{staging => driver-api}/remoteproc.rst | 2 +-
Documentation/{staging => driver-api}/rpmsg.rst | 4 ++--
Documentation/staging/index.rst | 2 --
MAINTAINERS | 4 ++--
5 files changed, 7 insertions(+), 7 deletions(-)
rename Documentation/{staging => driver-api}/remoteproc.rst (99%)
rename Documentation/{staging => driver-api}/rpmsg.rst (99%)
--
2.45.2
next reply other threads:[~2025-11-14 6:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 6:57 Daniel Baluta [this message]
2025-11-14 6:57 ` [PATCH 1/2] Documentation: Move rpmsg.rst and remoteproc.rst out of staging Daniel Baluta
2025-11-14 19:03 ` Randy Dunlap
2025-11-14 6:57 ` [PATCH 2/2] Documentation: Fix filenames for remoteproc/rpmsg Daniel Baluta
2025-11-14 10:29 ` Bagas Sanjaya
2025-11-14 11:33 ` Daniel Baluta
2025-11-14 13:35 ` Bagas Sanjaya
2025-11-14 15:39 ` Mathieu Poirier
2025-11-14 19:03 ` Randy Dunlap
2025-11-18 15:59 ` [PATCH 0/2] Documentation: Move rpmsg.rst and remoteproc.rst out of staging Mathieu Poirier
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=20251114065746.901649-1-daniel.baluta@nxp.com \
--to=daniel.baluta@nxp.com \
--cc=andersson@kernel.org \
--cc=arnaud.pouliquen@foss.st.com \
--cc=cedric.xing@intel.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=daniel.baluta@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mathieu.poirier@linaro.org \
--cc=pasha.tatashin@soleen.com \
--cc=rdunlap@infradead.org \
--cc=skhawaja@google.com \
--cc=taimoorzaeem@gmail.com \
--cc=yesanishhere@gmail.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