From: Bjorn Andersson <andersson@kernel.org>
To: srinivas.kandagatla@linaro.org, kuba@kernel.org,
konrad.dybcio@somainline.org, elder@kernel.org, kvalo@kernel.org,
edumazet@google.com, quic_jjohnson@quicinc.com,
mathieu.poirier@linaro.org, davem@davemloft.net,
agross@kernel.org, pabeni@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org,
netdev@vger.kernel.org, alsa-devel@alsa-project.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Make QMI message rules const
Date: Wed, 7 Dec 2022 09:53:26 -0600 [thread overview]
Message-ID: <167042840342.3235426.4288324926729574883.b4-ty@kernel.org> (raw)
In-Reply-To: <20220914234705.28405-1-quic_jjohnson@quicinc.com>
On Wed, 14 Sep 2022 16:47:01 -0700, Jeff Johnson wrote:
> Commit ff6d365898d4 ("soc: qcom: qmi: use const for struct
> qmi_elem_info") allows QMI message encoding/decoding rules to be
> const. So now update the definitions in the various clients to take
> advantage of this. Patches for ath10k and ath11k were previously sent
> separately.
>
> This series depends upon:
> https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git/commit/?h=for-next&id=ff6d365898d4d31bd557954c7fc53f38977b491c
>
> [...]
Applied, thanks!
[1/4] net: ipa: Make QMI message rules const
(no commit info)
[2/4] remoteproc: sysmon: Make QMI message rules const
commit: 7bd156cbbd0add4b869a7d997d057b76c329f4e5
[3/4] slimbus: qcom-ngd-ctrl: Make QMI message rules const
(no commit info)
[4/4] soc: qcom: pdr: Make QMI message rules const
(no commit info)
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2022-12-07 15:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 23:25 [PATCH 0/4] Make QMI message rules const Jeff Johnson
2022-09-12 23:25 ` [PATCH 1/4] net: ipa: " Jeff Johnson
2022-09-12 23:25 ` [PATCH 2/4] remoteproc: sysmon: " Jeff Johnson
2022-09-12 23:25 ` [PATCH 3/4] slimbus: qcom-ngd-ctrl: " Jeff Johnson
2022-09-12 23:25 ` [PATCH 4/4] soc: qcom: pdr: " Jeff Johnson
2022-09-14 10:18 ` Sibi Sankar
2022-09-14 10:26 ` [PATCH 3/4] slimbus: qcom-ngd-ctrl: " Sibi Sankar
2022-09-16 13:06 ` Srinivas Kandagatla
2022-09-16 15:20 ` Jeff Johnson
2022-09-14 10:24 ` [PATCH 2/4] remoteproc: sysmon: " Sibi Sankar
2022-09-14 10:22 ` [PATCH 1/4] net: ipa: " Sibi Sankar
2022-09-13 13:58 ` [PATCH 0/4] " Alex Elder
2022-09-13 18:51 ` Jeff Johnson
2022-09-13 20:21 ` Alex Elder
2022-09-13 22:19 ` Jeff Johnson
2022-09-15 18:47 ` Jeff Johnson
2022-09-14 23:47 ` [PATCH v2 " Jeff Johnson
2022-09-14 23:47 ` [PATCH v2 1/4] net: ipa: " Jeff Johnson
2022-10-18 21:17 ` [RESEND PATCH net-next] " Jeff Johnson
2022-10-21 12:20 ` patchwork-bot+netdevbpf
2022-09-14 23:47 ` [PATCH v2 2/4] remoteproc: sysmon: " Jeff Johnson
2022-09-14 23:47 ` [PATCH v2 3/4] slimbus: qcom-ngd-ctrl: " Jeff Johnson
2022-09-14 23:47 ` [PATCH v2 4/4] soc: qcom: pdr: " Jeff Johnson
2022-10-18 3:14 ` [PATCH v2 0/4] " Bjorn Andersson
2022-12-07 15:53 ` Bjorn Andersson [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=167042840342.3235426.4288324926729574883.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_jjohnson@quicinc.com \
--cc=srinivas.kandagatla@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;
as well as URLs for NNTP newsgroup(s).