From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"Wilcox, Matthew R" <matthew.r.wilcox@intel.com>,
Yinghai Lu <yinghai@kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: linux-next: IO BAR sizing warning
Date: Fri, 12 Jun 2009 07:39:29 +1000 [thread overview]
Message-ID: <1244756369.5739.51.camel@pasglop> (raw)
In-Reply-To: <20090611120739.012a0306@jbarnes-g45>
On Thu, 2009-06-11 at 12:07 -0700, Jesse Barnes wrote:
> > I am still getting the original warning. For reference, the following
> > architectures will probably have the same:
> >
> > ia64: 0xffffffffffffff
> > powerpc: ~(0UL)
> > sparc64: 0xffffffffffffffffUL
>
> Any comments here Ben? Seems this define is overloaded...
Ah, forgot to look at that. Will do ASAP.
Cheers,
Ben.
prev parent reply other threads:[~2009-06-11 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 4:30 linux-next: pci tree build warning Stephen Rothwell
2009-05-06 7:21 ` Yinghai Lu
2009-05-06 16:24 ` linux-next: IO BAR sizing warning Jesse Barnes
2009-05-06 17:41 ` Wilcox, Matthew R
2009-05-06 18:00 ` Jesse Barnes
2009-05-06 18:03 ` Wilcox, Matthew R
2009-06-03 6:49 ` Stephen Rothwell
2009-06-11 19:07 ` Jesse Barnes
2009-06-11 21:39 ` Benjamin Herrenschmidt [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=1244756369.5739.51.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-next@vger.kernel.org \
--cc=matthew.r.wilcox@intel.com \
--cc=sfr@canb.auug.org.au \
--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;
as well as URLs for NNTP newsgroup(s).