From: patchwork-bot+netdevbpf@kernel.org
To: Luca Weiss <luca.weiss@fairphone.com>
Cc: elder@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] More fixes for the IPA driver
Date: Sun, 12 Apr 2026 21:00:12 +0000 [thread overview]
Message-ID: <177602761230.3408407.17983223165088900536.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260409-ipa-fixes-v1-0-a817c30678ac@fairphone.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 09 Apr 2026 10:13:30 +0200 you wrote:
> Two more fixes for the Qualcomm IPA driver.
>
> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
> ---
> Luca Weiss (2):
> net: ipa: Fix programming of QTIME_TIMESTAMP_CFG
> net: ipa: Fix decoding EV_PER_EE for IPA v5.0+
>
> [...]
Here is the summary with links:
- [net,1/2] net: ipa: Fix programming of QTIME_TIMESTAMP_CFG
https://git.kernel.org/netdev/net/c/de08f9585692
- [net,2/2] net: ipa: Fix decoding EV_PER_EE for IPA v5.0+
https://git.kernel.org/netdev/net/c/1335b903cf2e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-12 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 8:13 [PATCH net 0/2] More fixes for the IPA driver Luca Weiss
2026-04-09 8:13 ` [PATCH net 1/2] net: ipa: Fix programming of QTIME_TIMESTAMP_CFG Luca Weiss
2026-04-09 8:17 ` Konrad Dybcio
2026-04-09 8:13 ` [PATCH net 2/2] net: ipa: Fix decoding EV_PER_EE for IPA v5.0+ Luca Weiss
2026-04-09 8:18 ` Konrad Dybcio
2026-04-12 21:00 ` patchwork-bot+netdevbpf [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=177602761230.3408407.17983223165088900536.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elder@kernel.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=phone-devel@vger.kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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