From: patchwork-bot+netdevbpf@kernel.org
To: Colin King <colin.king@canonical.com>
Cc: dchickles@marvell.com, sburla@marvell.com, fmanlunas@marvell.com,
davem@davemloft.net, kuba@kernel.org,
rvatsavayi@caviumnetworks.com, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] liquidio: Fix unintentional sign extension issue on left shift of u16
Date: Thu, 15 Jul 2021 17:40:04 +0000 [thread overview]
Message-ID: <162637080493.16853.1349424784773313835.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210714152343.144795-1-colin.king@canonical.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Wed, 14 Jul 2021 16:23:43 +0100 you wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Shifting the u16 integer oct->pcie_port by CN23XX_PKT_INPUT_CTL_MAC_NUM_POS
> (29) bits will be promoted to a 32 bit signed int and then sign-extended
> to a u64. In the cases where oct->pcie_port where bit 2 is set (e.g. 3..7)
> the shifted value will be sign extended and the top 32 bits of the result
> will be set.
>
> [...]
Here is the summary with links:
- liquidio: Fix unintentional sign extension issue on left shift of u16
https://git.kernel.org/netdev/net/c/e7efc2ce3d07
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:[~2021-07-15 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 15:23 [PATCH] liquidio: Fix unintentional sign extension issue on left shift of u16 Colin King
2021-07-15 17: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=162637080493.16853.1349424784773313835.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=dchickles@marvell.com \
--cc=fmanlunas@marvell.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rvatsavayi@caviumnetworks.com \
--cc=sburla@marvell.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