From: Matt Fleming <matt@codeblueprint.co.uk>
To: Tony Luck <tony.luck@intel.com>, Fenghua Yu <fenghua.yu@intel.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
Matt Fleming <matt@codeblueprint.co.uk>
Subject: [PATCH 0/5] ia64: Fix compiler warnings
Date: Wed, 04 May 2016 11:17:45 +0000 [thread overview]
Message-ID: <1462360670-27993-1-git-send-email-matt@codeblueprint.co.uk> (raw)
I routinely build ia64 kernels when merging EFI patches and for a
while now I've seen a bunch of warnings from GCC.
These patches silence those warnings, with the first patch fixing an
actual bug but the rest just making GCC happier.
NOTE: None of these patches have been runtime tested.
Matt Fleming (5):
ia64/PCI: Fix incorrect PCI resource end address
ia64/PCI: Remove unused 'addr' and fix build warning
ia64: Reduce stack usage by iterating over nodemask
ia64/traps: Silence GCC warning about uninitialised variable
ia64/unaligned: Silence another GCC warning about an uninitialised
variable
arch/ia64/kernel/traps.c | 1 +
arch/ia64/kernel/unaligned.c | 1 +
arch/ia64/sn/kernel/io_acpi_init.c | 1 -
arch/ia64/sn/kernel/io_init.c | 4 ++--
arch/ia64/sn/kernel/sn2/sn2_smp.c | 35 +++++++++++++++++++++++------------
5 files changed, 27 insertions(+), 15 deletions(-)
--
2.7.3
next reply other threads:[~2016-05-04 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 11:17 Matt Fleming [this message]
2016-05-04 11:17 ` [PATCH 1/5] ia64/PCI: Fix incorrect PCI resource end address Matt Fleming
2016-05-04 11:17 ` [PATCH 2/5] ia64/PCI: Remove unused 'addr' and fix build warning Matt Fleming
2016-05-04 11:17 ` [PATCH 3/5] ia64: Reduce stack usage by iterating over nodemask Matt Fleming
2016-05-04 11:17 ` [PATCH 4/5] ia64/traps: Silence GCC warning about uninitialised variable Matt Fleming
2016-05-04 11:17 ` [PATCH 5/5] ia64/unaligned: Silence another GCC warning about an " Matt Fleming
2016-05-05 19:59 ` [PATCH 0/5] ia64: Fix compiler warnings Luck, Tony
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=1462360670-27993-1-git-send-email-matt@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=fenghua.yu@intel.com \
--cc=helgaas@kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@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;
as well as URLs for NNTP newsgroup(s).