From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: imunsie@au1.ibm.com, linux-kernel@vger.kernel.org,
Matthew Wilcox <matthew@wil.cx>, Alex Chiang <achiang@hp.com>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] Avoid implicit constant truncation
Date: Tue, 2 Mar 2010 16:26:49 -0800 [thread overview]
Message-ID: <20100302162649.055c998b@jbarnes-piketon> (raw)
In-Reply-To: <4B8DA809.1040205@xenotime.net>
On Tue, 02 Mar 2010 16:06:33 -0800
Randy Dunlap <rdunlap@xenotime.net> wrote:
> On 03/02/10 16:01, imunsie@au1.ibm.com wrote:
> > From: Ian Munsie <imunsie@au.ibm.com>
> >
> > When building on 64 bit platforms, the compiler throws the following
> > warning:
> >
> > drivers/pci/probe.c:197: warning: large integer implicitly
> > truncated to unsigned type
> >
> > This patch adds an explicit truncation to silence the compiler
> > warning.
>
>
> Please see/read/use Documentation/SubmittingPatches. E.g.:
>
> The canonical patch subject line is:
>
> Subject: [PATCH 001/123] subsystem: summary phrase
>
> I.e., the subject: should tell us that this is a PCI: patch.
>
> (or even pci: -- i don't care which)
No need to resubmit though; I usually have to fix up the summary and
changelog a bit when applying anyway.
That said, this patch rings a bell; I think the warning is signalling a
real bug in the ppc code. IIRC Ben was going to look at it awhile
back, but I think it's mostly harmless so it's probably low on his list.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2010-03-03 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 0:01 imunsie
2010-03-03 0:06 ` Randy Dunlap
2010-03-03 0:09 ` Ian Munsie
2010-03-03 0:26 ` Jesse Barnes [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=20100302162649.055c998b@jbarnes-piketon \
--to=jbarnes@virtuousgeek.org \
--cc=achiang@hp.com \
--cc=bjorn.helgaas@hp.com \
--cc=imunsie@au1.ibm.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=rdunlap@xenotime.net \
/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
all inboxes | Powered by JetHome®