From: patchwork-bot+netdevbpf@kernel.org
To: Kumar@ci.codeaurora.org, M Chetan <m.chetan.kumar@linux.intel.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
johannes@sipsolutions.net, ryazanov.s.a@gmail.com,
loic.poulain@linaro.org, m.chetan.kumar@intel.com,
linuxwwan@intel.com, edumazet@google.com, pabeni@redhat.com
Subject: Re: [PATCH v2 net 0/4] net: wwan: iosm: fix build errors & bugs
Date: Mon, 28 Nov 2022 11:40:16 +0000 [thread overview]
Message-ID: <166963561631.6906.4335002623783242487.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221124103725.1445974-1-m.chetan.kumar@linux.intel.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 24 Nov 2022 16:07:25 +0530 you wrote:
> From: M Chetan Kumar <m.chetan.kumar@linux.intel.com>
>
> This patch series fixes iosm driver bugs & build errors.
>
> PATCH1: Fix kernel build robot reported error.
> PATCH2: Fix build error reported on armhf while preparing
> 6.1-rc5 for Debian.
> PATCH3: Fix UL throughput crash.
> PATCH4: Fix incorrect skb length.
>
> [...]
Here is the summary with links:
- [v2,net,1/4] net: wwan: iosm: fix kernel test robot reported error
https://git.kernel.org/netdev/net/c/985a02e75881
- [v2,net,2/4] net: wwan: iosm: fix dma_alloc_coherent incompatible pointer type
https://git.kernel.org/netdev/net/c/4a99e3c8ed88
- [v2,net,3/4] net: wwan: iosm: fix crash in peek throughput test
https://git.kernel.org/netdev/net/c/2290a1d46bf3
- [v2,net,4/4] net: wwan: iosm: fix incorrect skb length
https://git.kernel.org/netdev/net/c/c34ca4f32c24
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:[~2022-11-28 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 10:37 [PATCH v2 net 0/4] net: wwan: iosm: fix build errors & bugs m.chetan.kumar
2022-11-28 11:40 ` 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=166963561631.6906.4335002623783242487.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Kumar@ci.codeaurora.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linuxwwan@intel.com \
--cc=loic.poulain@linaro.org \
--cc=m.chetan.kumar@intel.com \
--cc=m.chetan.kumar@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ryazanov.s.a@gmail.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.