From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Mohammad Rafi Shaik <quic_mohs@quicinc.com>
Cc: 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, corbet@lwn.net,
quic_visr@quicinc.com
Subject: Re: [PATCH v5 0/2] Update section header name check
Date: Thu, 25 May 2023 09:32:00 -0600 [thread overview]
Message-ID: <ZG9/cEMRMg06Pz4u@p14s> (raw)
In-Reply-To: <f9c6fead-d573-a8bc-7e88-a53313ff8bef@quicinc.com>
On Thu, May 11, 2023 at 10:09:45PM +0530, Mohammad Rafi Shaik wrote:
>
> On 3/3/2023 3:27 AM, Mathieu Poirier wrote:
> > On Thu, Feb 23, 2023 at 08:35:57PM +0530, Mohammad Rafi Shaik wrote:
> > > Update section header name check and corresponding documentation.
> > > Changes since v4:
> > > -- Rephrase commit message.
> > Asked for clarifications on V4 that were never given to me. This patchset will
> > not move forward until those have been resolved.
> The present Qualcomm DSP binary contains resource table name as
> ".resource_table.ac_bin_process.",
My questions still haven't been answered:
1. Why do we have to change the kernel because of the way a company specific
tool generates an ELF?
2. Why is the "ac_bin_process" part needed at all?
> so the current logic with strcmp will fail with present comparision as the
> binary name is not only .resource_table but resource_table.ac_bin_process So
> to overcome this issue we modified the way of checking the resource table
> name to make it generic.
>
> strstarts(name_table + name, ".resource_table");
>
> This logic will perform a string comparison with name ".resouce_table"as our
> binary name is .resource_table.ac_bin_process it succeeds
>
> > > Changes since v3:
> > > -- Rephrase commit message.
> > > Changes since v2:
> > > -- Update the commit message with example.
> > > -- Update the documentation text appropriately.
> > > Changes since v1:
> > > -- Update the commit message.
> > > -- Use strstarts instead of strstr.
> > > -- Update documentation file.
> > >
> > > Srinivasa Rao Mandadapu (2):
> > > remoteproc: elf_loader: Update resource table name check
> > > docs: remoteproc: Update section header name requirement
> > >
> > > Documentation/staging/remoteproc.rst | 5 ++++-
> > > drivers/remoteproc/remoteproc_elf_loader.c | 2 +-
> > > 2 files changed, 5 insertions(+), 2 deletions(-)
> > >
> > > --
> > > 2.25.1
> > >
prev parent reply other threads:[~2023-05-25 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 15:05 [PATCH v5 0/2] Update section header name check Mohammad Rafi Shaik
2023-02-23 15:05 ` [PATCH v5 1/2] remoteproc: elf_loader: Update resource table " Mohammad Rafi Shaik
2023-02-23 15:05 ` [PATCH v5 2/2] docs: remoteproc: Update section header name requirement Mohammad Rafi Shaik
2023-03-02 21:57 ` [PATCH v5 0/2] Update section header name check Mathieu Poirier
[not found] ` <f9c6fead-d573-a8bc-7e88-a53313ff8bef@quicinc.com>
2023-05-25 15:32 ` Mathieu Poirier [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=ZG9/cEMRMg06Pz4u@p14s \
--to=mathieu.poirier@linaro.org \
--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=perex@perex.cz \
--cc=quic_mohs@quicinc.com \
--cc=quic_plai@quicinc.com \
--cc=quic_rohkumar@quicinc.com \
--cc=quic_visr@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;
as well as URLs for NNTP newsgroup(s).