From: Randy Dunlap <rdunlap@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>, linux-kernel@vger.kernel.org
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Selvin Xavier <selvin.xavier@broadcom.com>,
Devesh Sharma <devesh.sharma@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Subject: Re: Build regressions/improvements in v4.16-rc2 (infiniband/hw/bnxt_re)
Date: Mon, 19 Feb 2018 11:57:43 -0800 [thread overview]
Message-ID: <8c96847f-423d-1a90-3e67-feb409303675@infradead.org> (raw)
In-Reply-To: <1519048647-18732-1-git-send-email-geert@linux-m68k.org>
On 02/19/18 05:57, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v4.16-rc2[1] compared to v4.15[2].
Hi,
Just FYI, this driver could use some 32-bit attention.
> *** WARNINGS ***
>
> 1659 warning regressions:
bytes is larger than 1024 bytes [-Wframe-larger-than=]: => 78:1
> + /home/kisskb/slave/src/drivers/infiniband/hw/bnxt_re/ib_verbs.c: warning: left shift count >= width of type [enabled by default]: => 3550:2, 3552:4, 149:2
Above is due to:
#define BNXT_RE_MAX_MR_SIZE_HIGH BIT(39)
#define BNXT_RE_MAX_MR_SIZE BNXT_RE_MAX_MR_SIZE_HIGH
as 32-bit CPU cannot shift 39 bits left.
> + /home/kisskb/slave/src/drivers/infiniband/hw/bnxt_re/qplib_fp.c: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]: => 569:19
> + /home/kisskb/slave/src/drivers/infiniband/hw/bnxt_re/qplib_fp.c: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]: => 336:12, 333:23
> + /home/kisskb/slave/src/drivers/infiniband/hw/bnxt_re/qplib_fp.c: warning: passing argument 1 of '__fswab64' makes integer from pointer without a cast [enabled by default]: => 569:2
thanks
--
~Randy
prev parent reply other threads:[~2018-02-19 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 13:57 Build regressions/improvements in v4.16-rc2 Geert Uytterhoeven
2018-02-19 14:03 ` Geert Uytterhoeven
2018-02-19 19:57 ` Randy Dunlap [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=8c96847f-423d-1a90-3e67-feb409303675@infradead.org \
--to=rdunlap@infradead.org \
--cc=devesh.sharma@broadcom.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=selvin.xavier@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.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).