All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: elder@kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, elder@linaro.org,
	quic_sibis@quicinc.com
Subject: Re: [RESEND PATCH net-next] net: ipa: Make QMI message rules const
Date: Fri, 21 Oct 2022 12:20:17 +0000	[thread overview]
Message-ID: <166635481740.23176.9605046076231339926.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221018211718.23628-1-quic_jjohnson@quicinc.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Tue, 18 Oct 2022 14:17:18 -0700 you wrote:
> Commit ff6d365898d4 ("soc: qcom: qmi: use const for struct
> qmi_elem_info") allows QMI message encoding/decoding rules to be
> const, so do that for IPA.
> 
> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
> Reviewed-by: Alex Elder <elder@linaro.org>
> Reviewed-by: Sibi Sankar <quic_sibis@quicinc.com>
> 
> [...]

Here is the summary with links:
  - [RESEND,net-next] net: ipa: Make QMI message rules const
    https://git.kernel.org/netdev/net-next/c/c0facc045a14

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2022-10-21 12:21 UTC|newest]

Thread overview: 52+ 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 ` Jeff Johnson
2022-09-12 23:25 ` [PATCH 1/4] net: ipa: " Jeff Johnson
2022-09-12 23:25   ` Jeff Johnson
2022-09-12 23:25   ` [PATCH 2/4] remoteproc: sysmon: " Jeff Johnson
2022-09-12 23:25     ` Jeff Johnson
2022-09-12 23:25     ` [PATCH 3/4] slimbus: qcom-ngd-ctrl: " Jeff Johnson
2022-09-12 23:25       ` Jeff Johnson
2022-09-12 23:25       ` [PATCH 4/4] soc: qcom: pdr: " Jeff Johnson
2022-09-12 23:25         ` Jeff Johnson
2022-09-14 10:18         ` Sibi Sankar
2022-09-14 10:18           ` Sibi Sankar
2022-09-14 10:26       ` [PATCH 3/4] slimbus: qcom-ngd-ctrl: " Sibi Sankar
2022-09-14 10:26         ` Sibi Sankar
2022-09-16 13:06       ` Srinivas Kandagatla
2022-09-16 13:06         ` Srinivas Kandagatla
2022-09-16 15:20         ` Jeff Johnson
2022-09-16 15:20           ` Jeff Johnson
2022-09-14 10:24     ` [PATCH 2/4] remoteproc: sysmon: " Sibi Sankar
2022-09-14 10:24       ` Sibi Sankar
2022-09-14 10:22   ` [PATCH 1/4] net: ipa: " Sibi Sankar
2022-09-14 10:22     ` Sibi Sankar
2022-09-13 13:58 ` [PATCH 0/4] " Alex Elder
2022-09-13 13:58   ` Alex Elder
2022-09-13 18:51   ` Jeff Johnson
2022-09-13 18:51     ` Jeff Johnson
2022-09-13 20:21     ` Alex Elder
2022-09-13 20:21       ` Alex Elder
2022-09-13 22:19       ` Jeff Johnson
2022-09-13 22:19         ` Jeff Johnson
2022-09-15 18:47   ` Jeff Johnson
2022-09-15 18:47     ` Jeff Johnson
2022-09-14 23:47 ` [PATCH v2 " Jeff Johnson
2022-09-14 23:47   ` Jeff Johnson
2022-09-14 23:47   ` [PATCH v2 1/4] net: ipa: " Jeff Johnson
2022-09-14 23:47     ` Jeff Johnson
2022-10-18 21:17     ` [RESEND PATCH net-next] " Jeff Johnson
2022-10-21 12:20       ` patchwork-bot+netdevbpf [this message]
2022-09-14 23:47   ` [PATCH v2 2/4] remoteproc: sysmon: " Jeff Johnson
2022-09-14 23:47     ` Jeff Johnson
2022-10-18 20:44     ` [RESEND PATCH] " Jeff Johnson
2022-09-14 23:47   ` [PATCH v2 3/4] slimbus: qcom-ngd-ctrl: " Jeff Johnson
2022-09-14 23:47     ` Jeff Johnson
2022-10-18 22:25     ` [RESEND PATCH] " Jeff Johnson
2022-10-18 22:25       ` Jeff Johnson
2022-09-14 23:47   ` [PATCH v2 4/4] soc: qcom: pdr: " Jeff Johnson
2022-09-14 23:47     ` Jeff Johnson
2022-10-05 20:54     ` [RESEND] " Jeff Johnson
2022-10-18  3:14   ` [PATCH v2 0/4] " Bjorn Andersson
2022-10-18  3:14     ` Bjorn Andersson
2022-12-07 15:53   ` Bjorn Andersson
2022-12-07 15:53     ` 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=166635481740.23176.9605046076231339926.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=elder@kernel.org \
    --cc=elder@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=quic_jjohnson@quicinc.com \
    --cc=quic_sibis@quicinc.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 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.