public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Yinghai Lu <yinghai@kernel.org>, Aaron Ma <mapengyu@gmail.com>
Subject: linux-next: build warning after merge of the pci-current tree
Date: Mon, 17 Nov 2014 10:02:20 +1100	[thread overview]
Message-ID: <20141117100220.0e503957@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 626 bytes --]

Hi Bjorn,

After merging the pci-current tree, today's linux-next build
(arm_multi_v7_defconfig) produced this warning:

drivers/pci/probe.c: In function 'pci_read_bridge_mmio_pref':
drivers/pci/probe.c:438:5: warning: left shift count >= width of type
     base |= ((dma_addr_t) mem_base_hi) << 32;
     ^
drivers/pci/probe.c:439:5: warning: left shift count >= width of type
     limit |= ((dma_addr_t) mem_limit_hi) << 32;
     ^

Introduced by commit 3a02517d5e2a ("PCI: Support 64-bit bridge windows
if we have 64-bit dma_addr_t").

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2014-11-16 23:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-16 23:02 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-31  1:58 linux-next: build warning after merge of the pci-current tree Stephen Rothwell
2024-01-31  7:42 ` Johan Hovold
2024-01-31 15:07   ` Bjorn Helgaas
2012-11-05 23:05 Stephen Rothwell

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=20141117100220.0e503957@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mapengyu@gmail.com \
    --cc=yinghai@kernel.org \
    /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