From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jon Hunter <jonathanh@nvidia.com>,
Vidya Sagar <vidyas@nvidia.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-pci@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] PCI: tegra: Fix shiftTooManyBitsSigned warning for Tegra194
Date: Wed, 23 Jun 2021 16:23:20 +0100 [thread overview]
Message-ID: <162446177943.19852.7323663097557808562.b4-ty@arm.com> (raw)
In-Reply-To: <20210618160219.303092-1-jonathanh@nvidia.com>
On Fri, 18 Jun 2021 17:02:19 +0100, Jon Hunter wrote:
> The cppcheck tool issues the following warning for the Tegra194 PCIe
> driver ...
>
> $ cppcheck --enable=all drivers/pci/controller/dwc/pcie-tegra194.c
> Checking drivers/pci/controller/dwc/pcie-tegra194.c ...
>
> drivers/pci/controller/dwc/pcie-tegra194.c:1829:23: portability:
> Shifting signed 32-bit value by 31 bits is
> implementation-defined behaviour. See condition at line 1826.
> [shiftTooManyBitsSigned]
>
> [...]
Applied to pci/tegra, thanks!
[1/1] PCI: tegra194: Fix shiftTooManyBitsSigned warning for Tegra194
https://git.kernel.org/lpieralisi/pci/c/b1eca3a544
Thanks,
Lorenzo
prev parent reply other threads:[~2021-06-23 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 16:02 [PATCH] PCI: tegra: Fix shiftTooManyBitsSigned warning for Tegra194 Jon Hunter
2021-06-18 16:05 ` Jon Hunter
2021-06-18 23:04 ` Bjorn Helgaas
2021-06-23 8:52 ` Lorenzo Pieralisi
2021-06-23 12:04 ` Bjorn Helgaas
2021-06-24 23:01 ` Bjorn Helgaas
2021-06-25 9:08 ` Lorenzo Pieralisi
2021-06-23 15:23 ` Lorenzo Pieralisi [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=162446177943.19852.7323663097557808562.b4-ty@arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=jonathanh@nvidia.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vidyas@nvidia.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.