From: patchwork-bot+netdevbpf@kernel.org
To: Valentina Goncharenko <goncharenko.vp@ispras.ru>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, jringle@gridpoint.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH 1/2] net: encx24j600: Add parentheses to fix precedence
Date: Mon, 05 Dec 2022 09:50:15 +0000 [thread overview]
Message-ID: <167023381566.8030.441453693172726774.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221201173408.26954-1-goncharenko.vp@ispras.ru>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 1 Dec 2022 20:34:07 +0300 you wrote:
> In functions regmap_encx24j600_phy_reg_read() and
> regmap_encx24j600_phy_reg_write() in the conditions of the waiting
> cycles for filling the variable 'ret' it is necessary to add parentheses
> to prevent wrong assignment due to logical operations precedence.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> [...]
Here is the summary with links:
- [1/2] net: encx24j600: Add parentheses to fix precedence
https://git.kernel.org/netdev/net/c/167b3f2dcc62
- [2/2] net: encx24j600: Fix invalid logic in reading of MISTAT register
https://git.kernel.org/netdev/net/c/25f427ac7b8d
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-12-05 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 17:34 [PATCH 1/2] net: encx24j600: Add parentheses to fix precedence Valentina Goncharenko
2022-12-01 17:34 ` [PATCH 2/2] net: encx24j600: Fix invalid logic in reading of MISTAT register Valentina Goncharenko
2022-12-02 7:55 ` Pavan Chebbi
2022-12-02 7:50 ` [PATCH 1/2] net: encx24j600: Add parentheses to fix precedence Pavan Chebbi
2022-12-05 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=167023381566.8030.441453693172726774.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=goncharenko.vp@ispras.ru \
--cc=jringle@gridpoint.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).