From: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
linux-remoteproc@vger.kernel.org, agross@kernel.org,
andersson@kernel.org, lgirdwood@gmail.com, broonie@kernel.org,
robh+dt@kernel.org, quic_plai@quicinc.com, bgoswami@quicinc.com,
perex@perex.cz, tiwai@suse.com, srinivas.kandagatla@linaro.org,
quic_rohkumar@quicinc.com, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, swboyd@chromium.org,
judyhsiao@chromium.org, devicetree@vger.kernel.org,
krzysztof.kozlowski@linaro.org, mathieu.poirier@linaro.org,
corbet@lwn.net
Subject: Re: [PATCH v2 2/2] docs: remoteproc: Update section header name requirement
Date: Tue, 20 Dec 2022 12:57:35 +0530 [thread overview]
Message-ID: <b4150898-d5f0-894d-2c69-b98e56142481@quicinc.com> (raw)
In-Reply-To: <ac2d90e2-6fc3-98dc-8c73-936132b6c8d5@linaro.org>
On 12/15/2022 12:55 PM, Philippe Mathieu-Daudé wrote:
Thanks for your time Phil!!!
> On 13/12/22 10:48, Srinivasa Rao Mandadapu wrote:
>> Add section header name requirement specification in elf segments.
>>
>> Signed-off-by: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>
>> ---
>> Documentation/staging/remoteproc.rst | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/Documentation/staging/remoteproc.rst
>> b/Documentation/staging/remoteproc.rst
>> index 348ee7e..3125030 100644
>> --- a/Documentation/staging/remoteproc.rst
>> +++ b/Documentation/staging/remoteproc.rst
>> @@ -245,6 +245,8 @@ if the remote processor is accessing memory
>> directly).
>> In addition to the standard ELF segments, most remote processors
>> would
>> also include a special section which we call "the resource table".
>> +This resource table section name may have anything appended after it,
>> +but it must start with ".resource_table"
>
> What do you think of:
>
> In addition to the standard ELF segments, most remote processors would
> also include a special section which we call the "resource table".
> A "resource table" section name must start with the ".resource_table"
> prefix, optionally having a more descriptive string appended. For
> example, ".resource_table.my_rproc" is a valid section name.
Okay. Will change accordingly and re-spin the patch set.
>
> Regards,
>
> Phil.
prev parent reply other threads:[~2022-12-20 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 9:48 [PATCH v2 0/2] Update section header name check Srinivasa Rao Mandadapu
2022-12-13 9:48 ` [PATCH v2 1/2] remoteproc: elf_loader: Update resource table " Srinivasa Rao Mandadapu
2022-12-15 7:06 ` Philippe Mathieu-Daudé
2022-12-20 7:32 ` Srinivasa Rao Mandadapu
2022-12-13 9:48 ` [PATCH v2 2/2] docs: remoteproc: Update section header name requirement Srinivasa Rao Mandadapu
2022-12-15 7:25 ` Philippe Mathieu-Daudé
2022-12-20 7:27 ` Srinivasa Rao Mandadapu [this message]
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=b4150898-d5f0-894d-2c69-b98e56142481@quicinc.com \
--to=quic_srivasam@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bgoswami@quicinc.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=judyhsiao@chromium.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=perex@perex.cz \
--cc=philmd@linaro.org \
--cc=quic_plai@quicinc.com \
--cc=quic_rohkumar@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=swboyd@chromium.org \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®