From: Alex Elder <elder@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: andersson@kernel.org, agross@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, elder@kernel.org,
linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Luca Weiss <luca.weiss@fairphone.com>
Subject: Re: [PATCH net-next 2/2] net: ipa: add IPA v4.7 support
Date: Fri, 30 Dec 2022 17:53:19 -0600 [thread overview]
Message-ID: <4bd03a34-7de9-2ae4-ff82-df2470b92ea5@linaro.org> (raw)
In-Reply-To: <20b2f7c3-6481-eabf-7c46-f5f38d258c62@linaro.org>
On 12/30/22 11:28 AM, Alex Elder wrote:
>
> Anyway, for a given SoC, the whole IMEM region is used
> by different entities. For SM7550, for example, it is
NOTE: This is a typo. I meant SM7250 above.
> divided into 6 parts of various sizes (100KB, 24KB, 32KB,
> 8KB, 8KB, and 4KB). For IPA on this SoC, the offset is
> 0x146a9000, with size 0x2000. Hence the range defined
> above.
Konrad pointed out the error, I just want to be sure
it's corrected so it's clear...
-Alex
next prev parent reply other threads:[~2022-12-30 23:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 21:15 [PATCH net-next 0/2] net: ipa: enable IPA v4.7 support Alex Elder
2022-12-08 21:15 ` [PATCH net-next 1/2] dt-bindings: net: qcom,ipa: Add SM6350 compatible Alex Elder
2022-12-09 8:24 ` Krzysztof Kozlowski
2022-12-30 20:50 ` Caleb Connolly
2022-12-08 21:15 ` [PATCH net-next 2/2] net: ipa: add IPA v4.7 support Alex Elder
2022-12-08 21:22 ` Konrad Dybcio
2022-12-09 20:22 ` Alex Elder
2022-12-10 9:31 ` Konrad Dybcio
2022-12-12 23:54 ` Jakub Kicinski
2022-12-13 1:11 ` Alex Elder
2022-12-30 17:28 ` Alex Elder
2022-12-30 23:53 ` Alex Elder [this message]
2022-12-13 0:00 ` [PATCH net-next 0/2] net: ipa: enable " patchwork-bot+netdevbpf
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=4bd03a34-7de9-2ae4-ff82-df2470b92ea5@linaro.org \
--to=elder@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.