From: Bjorn Helgaas <helgaas@kernel.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: ying.huang@intel.com, linux-pci@vger.kernel.org
Subject: Re: [bug report] ACPI, APEI, Add PCIe AER error information printing support
Date: Thu, 13 Oct 2016 12:55:13 -0500 [thread overview]
Message-ID: <20161013175513.GA21529@localhost> (raw)
In-Reply-To: <20161013065847.GA30382@mwanda>
On Thu, Oct 13, 2016 at 09:58:47AM +0300, Dan Carpenter wrote:
> Hello Huang Ying,
>
> The patch c413d7682020: "ACPI, APEI, Add PCIe AER error information
> printing support" from Feb 21, 2011, leads to the following static
> checker warning:
>
> drivers/pci/pcie/aer/aerdrv_errprint.c:229 cper_print_aer()
> warn: bool comparison is always 'false'
Hi Dan,
Thanks a lot for the report. Do you have any plans for integrating
smatch into the kernel build process like sparse is? I think I did
figure out how to run smatch myself, but it wasn't quite as easy as
"apt-get install sparse; make C=2".
Bjorn
next prev parent reply other threads:[~2016-10-13 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 6:58 [bug report] ACPI, APEI, Add PCIe AER error information printing support Dan Carpenter
2016-10-13 17:55 ` Bjorn Helgaas [this message]
2016-10-14 8:31 ` Dan Carpenter
2016-10-14 8:43 ` Huang, Ying
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=20161013175513.GA21529@localhost \
--to=helgaas@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=linux-pci@vger.kernel.org \
--cc=ying.huang@intel.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