From: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
To: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org,
Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
Subject: [PATCH v3 1/5] MAINTAINERS: add rsc_table.h to remoteproc entry
Date: Mon, 3 Aug 2026 17:13:27 +0530 [thread overview]
Message-ID: <20260803114331.3277263-2-mukesh.ojha@oss.qualcomm.com> (raw)
In-Reply-To: <20260803114331.3277263-1-mukesh.ojha@oss.qualcomm.com>
include/linux/rsc_table.h was split out from include/linux/remoteproc.h
to hold the resource table wire-format definitions. Add it to the
REMOTEPROC entry so it is covered by the same maintainers.
Signed-off-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 56b337a06447..433d737dc595 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -22957,6 +22957,7 @@ F: Documentation/devicetree/bindings/remoteproc/
F: Documentation/staging/remoteproc.rst
F: drivers/remoteproc/
F: include/linux/remoteproc.h
+F: include/linux/rsc_table.h
F: include/linux/remoteproc/
REMOTE PROCESSOR MESSAGING (RPMSG) SUBSYSTEM
--
2.53.0
next prev parent reply other threads:[~2026-08-03 11:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 11:43 [PATCH v3 0/5] remoteproc: Misc. RSC table changes Mukesh Ojha
2026-08-03 11:43 ` Mukesh Ojha [this message]
2026-08-03 11:43 ` [PATCH v3 2/5] remoteproc: fix coding style issues in remoteproc.h Mukesh Ojha
2026-08-03 11:43 ` [PATCH v3 3/5] remoteproc: replace BSD blurb with SPDX identifier " Mukesh Ojha
2026-08-03 11:43 ` [PATCH v3 4/5] remoteproc: replace BSD blurb with SPDX identifier in rsc_table.h Mukesh Ojha
2026-08-03 11:43 ` [PATCH v3 5/5] remoteproc: fix OOB read via signed offset in rsc_table_for_each_entry() Mukesh Ojha
2026-08-04 22:12 ` Bjorn Andersson
2026-08-05 3:34 ` [PATCH v3 0/5] remoteproc: Misc. RSC table changes Bjorn Andersson
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=20260803114331.3277263-2-mukesh.ojha@oss.qualcomm.com \
--to=mukesh.ojha@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.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
all inboxes | Powered by JetHome®