From: patchwork-bot+netdevbpf@kernel.org
To: Pietro Borrello <borrello@diag.uniroma1.it>
Cc: santosh.shilimkar@oracle.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
willemb@google.com, c.giuffrida@vu.nl, h.j.bos@vu.nl,
jkl820.git@gmail.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] rds: rds_rm_zerocopy_callback() use list_first_entry()
Date: Thu, 09 Feb 2023 09:50:17 +0000 [thread overview]
Message-ID: <167593621777.24180.14940979671887283840.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230202-rds-zerocopy-v3-1-83b0df974f9a@diag.uniroma1.it>
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 07 Feb 2023 18:26:34 +0000 you wrote:
> rds_rm_zerocopy_callback() uses list_entry() on the head of a list
> causing a type confusion.
> Use list_first_entry() to actually access the first element of the
> rs_zcookie_queue list.
>
> Fixes: 9426bbc6de99 ("rds: use list structure to track information for zerocopy completion notification")
> Reviewed-by: Willem de Bruijn <willemb@google.com>
> Signed-off-by: Pietro Borrello <borrello@diag.uniroma1.it>
>
> [...]
Here is the summary with links:
- [net,v3] rds: rds_rm_zerocopy_callback() use list_first_entry()
https://git.kernel.org/netdev/net/c/f753a68980cf
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:[~2023-02-09 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 18:26 [PATCH net v3] rds: rds_rm_zerocopy_callback() use list_first_entry() Pietro Borrello
2023-02-09 9:50 ` 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=167593621777.24180.14940979671887283840.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=borrello@diag.uniroma1.it \
--cc=c.giuffrida@vu.nl \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=h.j.bos@vu.nl \
--cc=jkl820.git@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.com \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox